Changes between Version 44 and Version 45 of DevWikiComitGuidelines

Timestamp:

May 17, 2011, 3:24:01 AM (13 years ago)

Author:

robe

Comment:

—

DevWikiComitGuidelines

@@ -38 +38 @@
 == Code Conventions ==
   * C code should follow our designated [http://trac.osgeo.org/postgis/browser/trunk/STYLE Style Guidelines] to the best of your abilities
+  * All source code in SVN should be in Unix text format as opposed to DOS text mode.
 
 == SVN Administrator ==
@@ -59 +60 @@
     * 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.
     * 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.
-    * 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.
-    * All source code in SVN should be in Unix text format as opposed to DOS text mode.
+    * 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.   
   
     * 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.
@@ -105 +105 @@
     * If there is uncertainty about whether a change is proper to contribute to the code base, please seek more information from the project steering committee, or the foundation legal counsel. 
     * New contributors and company contributors should be added to the credits in doc/introduction.xml of the latest release of the PostGIS manual.
+    * It is the responsibility of the document lead to insure when new enhancements are added or breaking changes are made, these are 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. 
 
 == Bootstrapping ==