Changes between Version 12 and Version 13 of DevWikiComitGuidelines
- Timestamp:
- 02/24/11 00:09:17 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DevWikiComitGuidelines
v12 v13 57 57 * 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. 58 58 * In the event of buildbot failure notice, the person who caused the break must fix the break before working on anything else 59 60 == Relationship with other Projects == 61 62 Some parts of the PostGIS code base are dependent on other upsteam projects or other projects rely on functionality in PostGIS. So changes in those areas should go first into those upstream projects and in event of major changes to PostGIS, said projects should be regression tested (before a PostGIS release) to ensure the latest version still works with the latest RTM version of PostGIS. 63 64 Currently the list of those areas is : 65 66 * postgresql ( http://www.postgresql.org) 67 * geos ( http://geos.osgeo.org) 68 * proj ( http://proj.osgeo.org) 69