Changes between Version 55 and Version 56 of DevWikiComitGuidelines
- Timestamp:
- 05/17/11 04:26:26 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DevWikiComitGuidelines
v55 v56 24 24 25 25 New committers are responsible for having read, and understood this document. 26 27 == Committer Tracking ==28 29 A list of all project committers will be kept in the main postgis directory in a file called (CREDITS) listing for each SVN committer:30 31 * Userid: the id that will appear in the SVN logs for this person.32 * Full name: the users actual name.33 * Email address: A current email address at which the committer can be reached. It may be altered in normal ways to make it harder to auto-harvest.34 * A brief indication of areas of responsibility.35 * The name of key developers and thier area of responsibility should also be prominently shown in latest release of manual in the doc/introduction.xml file.36 This will be the responsibility of the documentation lead to ensure.37 26 38 27 == Code and Documentation Conventions == … … 64 53 12. 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. 65 54 13. 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 55 56 == Committer Tracking == 57 58 A list of all project committers will be kept in the main postgis directory in a file called (CREDITS) listing for each SVN committer: 59 60 * Userid: the id that will appear in the SVN logs for this person. 61 * Full name: the users actual name. 62 * Email address: A current email address at which the committer can be reached. It may be altered in normal ways to make it harder to auto-harvest. 63 * A brief indication of areas of responsibility. 64 * The name of key developers and thier area of responsibility should also be prominently shown in latest release of manual in the doc/introduction.xml file. 65 This will be the responsibility of the documentation lead to ensure. 66 66 67 67 == Relationship with other Projects ==