Changes between Version 6 and Version 7 of RFC2


Ignore:
Timestamp:
Apr 18, 2008, 8:38:28 AM (16 years ago)
Author:
pramsey
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • RFC2

    v6 v7  
    1515
    1616Permission for SVN commit access shall be provided to new developers only if accepted by the [wiki:PSC GEOS Project Steering Committee]. A proposal should be written to the PSC for new committers and voted on normally. It is not necessary to write an RFC document for these votes, a proposal to [http://lists.osgeo.org/mailman/listinfo/geos-devel geos-devel] is sufficient.
     17
     18Every developer position in the project is represented by an individual, and commit access will be granted to individuals only, group accounts are not permitted.
    1719
    1820Removal of SVN commit access should be handled by the same process.
    … …  
    7577 * All source code in SVN should be in Unix text format as opposed to DOS text mode.
    7678 * 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 [wiki: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.
     79* Every commit introducing new feature '''should''' be covered with corresponding test case included to the GEOS set of unit tests (trunk/tests/unit).
    7780
    7881