*** CVS USAGE ***

Bugfixes and cosmetics should be made on the HEAD branch of the CVS.
Major changes should be done on another branch and be merged soon.


LOG MESSAGES
------------

ChangeLog is generated by your commit messages, you should put meaningful
information, unless you made changes that are too trivial to be mentioned.
Commit info when merging a branch with the HEAD must be very informative.

Non trivial commits should be related to a specific item (task or bug). 
Always include the id of the item, for instance by concluding your 
log message by (bug #nnnn).


AVOIDING MERGE CONFLICTS
------------------------

When active development is going on on a specific branch, avoid commits on the 
same part of the code; ask if it is possible to commit on the active branch.
Or make a branch on the branch.


BRANCH NAMING
-------------

At some points it's useful to tag the CVS. To keep something easily
readable, I propose the following Tag name policy:
	nature of the change _ YYYY-MM-DD _ info about the change.
Basically, all tags that are only for development purpose should be like
	DEV_2003-09-05_blabla
Tag for release purpose should be like
	REL_2003-09-05_1-0-1beta




EOF