Changes between Version 27 and Version 28 of DevWikiComitGuidelines


Ignore:
Timestamp:
Apr 26, 2011, 2:17:16 PM (13 years ago)
Author:
robe
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • DevWikiComitGuidelines

    v27 v28  
    5050    * Significant changes to the main development version should be discussed on the postgis-dev list before you make them, and larger changes will require an RFC approved by the PSC.
    5151    * Do not create new branches (except for spike branches) without the approval of the PSC. Release managers are assumed to have permission to create a branch.
    52     * spike branch (those in the spike/username area are to be used for experimentation or for major code refactorings that will destabilize the trunk.  After such experimentation is stable, this can then be merged into the trunk after approval from PSC members.
     52    * spike branch (those in the spike/username area are to be used for experimentation or for major code refactorings that will destabilize the trunk.  After such experimentation is deemed stable, this can then be merged into the trunk after approval from PSC members.
    5353    * All source code in SVN should be in Unix text format as opposed to DOS text mode.
    5454    * C code should follow our designated A-style format and astyle should be applied before commit
    55     * When committing new features or significant changes to existing source code, the committer should take reasonable measures to insure that the source code continues to build and work on the most commonly supported platforms (currently Linux and Windows), either by testing on those platforms directly, running Buildbot tests, or by getting help from other developers working on those platforms. If new files or library dependencies are added, then the configure.in, Makefile.in, Makefile.vc and related documentations should be kept up to date.
     55    * When committing new features or significant changes to existing source code, the committer should take reasonable measures to insure that the source code continues to build and work on the most commonly supported platforms (currently Linux and Windows), either by testing on those platforms directly, running Buildbot tests, or by getting help from other developers working on those platforms. If new files or library dependencies are added, then the configure.in, Makefile.in and related documentations should be kept up to date.
    5656    * In the event of broken build (build bot fail notification), the person who broke the build must fix the break before working on anything else
    5757