Context Navigation

Changes between Version 29 and Version 30 of DevWikiComitGuidelines

v29	v30
42	42	* Use meaningful descriptions for commit log entries.
43	43	* 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 hyperlink from the changeset to the mentionned ticket.
44		* When new enhancements are added or breaking changes are made, these should be noted in the trunk/NEWS or relevant branch/NEWS as soon as conveniently possible. The note should include the trac # and contributors to the feature/change
	44	* When new enhancements are added or breaking changes are made, these should be noted in the trunk/NEWS or relevant branch/NEWS as soon as conveniently possible. The note should include the trac # and contributors to the feature/change. Once a new feature ticket is completed, it should have in '''keywords''' section of ticket with '''history'''. This will better ensure it is not forgotten when preparing the news release.
45	45	* 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.
46	46	* 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.