URL:
<http://gna.org/cookbook/?func=detailitem&item_id=124>
Summary/Question: SVN Usage Rules
Project: Savane
Submitted by: yeupou
Submitted on: vendredi 25.11.2005 à 11:42
Category: None
Importance: 3 - Normal
Status: Approved
Privacy: Public
Assigned to: None
Open/Closed: Open
_______________________________________________________
Details:
ugfixes and cosmetics should be made on the trunk of SVN.
Please post a bug report before starting on a bugfixes. Other developers may
have clues about what seems to be a bug.
Major changes should be done on another branch and be merged soon.
Before creating a branch, always post a task, so we can easily track what it
will do and how and when to merge it.
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).
<u>Always include the id of the item</u>, for instance by ending 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/TAGS NAMING
------------------
At some points it's useful to tag the SVN.
To keep something easily readable, I propose the following Tag name policy:
nature of the change-YYYY.MM-info about the change.
Basically, all tags that are only for development purpose should be like
DEV-2003.09-blabla_and_blublo
Tag for release purpose should be like
REL-2003.0-prerelease1
or
REL-1.3
(Release tags of the days of CVS are a bit different, but that's not a big
deal).
_______________________________________________________
Reply to this item at:
<http://gna.org/cookbook/?func=detailitem&item_id=124>
_______________________________________________
Message posté via/par Gna!
http://gna.org/
_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev
