Changes between Version 4 and Version 5 of rfc3_commiters
- Timestamp:
- Mar 2, 2010, 11:56:50 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
rfc3_commiters
v4 v5 60 60 61 61 * Use meaningful descriptions for SVN commit log entries. 62 * Add a bug reference like "(bug 1232)" at the end of SVN commit log entries when committing changes related to a bug in bugzilla. 62 * Add a bug reference like "(#1232)" at the end of SVN commit log entries when committing changes related to a ticket in Trac. The '#' character enables Trac to create a hypelink from the changeset to the mentionned ticket. 63 * After commiting changes related to a ticket in Trac, write the tree and revision in which it was fixed in the ticket description. Such as "Fixed in trunk (r12345) and in branches/1.7 (r12346)". The 'r' character enables Trac to create a hyperlink from the ticket to the changeset. 63 64 * Changes should not be committed in stable branches without a corresponding bug id. Any change worth pushing into the stable version is worth a bug entry. 64 65 * Never commit new features to a stable branch without permission of the PSC or release manager. Normally only fixes should go into stable branches.