Changes between Version 36 and Version 37 of DevWikiComitGuidelines
- Timestamp:
- 05/13/11 23:52:05 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DevWikiComitGuidelines
v36 v37 55 55 * 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. 56 56 * All source code in SVN should be in Unix text format as opposed to DOS text mode. 57 * C code should follow our designated A-styleformat and astyle should be applied before commit57 * C code should follow our designated [http://trac.osgeo.org/postgis/browser/trunk/STYLE A-style] format and astyle should be applied before commit 58 58 * 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. 59 59 * 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