Changes between Version 45 and Version 46 of DevWikiComitGuidelines


Ignore:
Timestamp:
May 17, 2011, 3:27:16 AM (13 years ago)
Author:
robe
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • DevWikiComitGuidelines

    v45 v46  
    11= RFC-5: PostGIS Committer Guidelines =
    22
    3 ||Version:|| 1.00000008
     3||Version:|| 1.00000009
    44||Author:|| Regina Obe <lr at pcorp dot us>||
    55||Last Edited:|| 2011/05/14||
    … …  
    3636      This will be the responsibility of the documentation lead to ensure.
    3737
    38 == Code Conventions ==
     38== Code and Documentation Conventions ==
    3939  * C code should follow our designated [http://trac.osgeo.org/postgis/browser/trunk/STYLE Style Guidelines] to the best of your abilities
    4040  * All source code in SVN should be in Unix text format as opposed to DOS text mode.
    … …  
    5252    * Use meaningful descriptions for commit log entries.
    5353    * 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.
    54     * 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.
     54    * When new enhancements are added or breaking changes are made and completed the related ticket should have in '''keywords''' section of ticket with '''history'''.  This will better ensure it is not forgotten when preparing the news release.
    5555    * 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.
    5656    * 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.