Changes between Version 68 and Version 69 of DevWikiComitGuidelines


Ignore:
Timestamp:
Oct 16, 2017, 12:55:07 PM (4 years ago)
Author:
robe
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DevWikiComitGuidelines

    v68 v69  
    33||Version:|| 1.00000014
    44||Author:|| Regina Obe <lr at pcorp dot us>||
    5 ||Last Edited:|| 2017/11/13||
     5||Last Edited:|| 2017/10/16||
    66||Status:|| Approved||
    77
     
    5656    13. spike branch (those in the spike/username area are to be used for experimentation or for major code refactoring that will destabilize the trunk.  After such experimentation is deemed stable, this can then be merged into the trunk after approval from PSC members.  Using a git repo for experimentation instead of svn/spike is the preferred mode of experimentation these days.
    5757    14. 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, Mac, 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.
    58     15. After each commit, verify that all the build bots are happy on this page - https://trac.osgeo.org/postgis/ and if they issue is caused by your commit, fix it before making any more changes.
     58    15. After each commit, verify that all the build bots are happy on this page - https://trac.osgeo.org/postgis/ and if their unhappiness is caused by your commit, fix the issue before making any other changes.
    5959
    6060== Committer Tracking ==