Changes between Version 13 and Version 14 of RFC2


Ignore:
Timestamp:
Jun 25, 2018, 12:56:25 AM (4 years ago)
Author:
robe
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RFC2

    v13 v14  
    7373The following are considered good SVN commit practices for the GEOS project.
    7474
    75  * Use meaningful descriptions for SVN commit log entries.
     75 * Use meaningful descriptions for commit log entries.
    7676
    77  * Add a bug reference like "(#1232)" at the end of SVN commit log entries when committing changes related to an existing [wiki:TracTickets Ticket] in the GEOS Trac database, so it's properly linked on the Trac pages (see [wiki:TracLinks])
     77 * Add a bug reference like "references #1232" or "closes #1232" at the end of the commit log entries when committing changes related to an existing [wiki:TracTickets Ticket] in the GEOS Trac database, so it's properly linked on the Trac pages (see [wiki:TracLinks])
    7878
    7979 * Changes should not be committed in stable branches without a corresponding [wiki:TracTickets Ticket] number. Any change worth pushing into the stable version is worth a [wiki:TracTickets Ticket] entry.
     
    8787 * Do not create new SVN [http://en.wikipedia.org/wiki/Branching_(software) branches] without the approval of the [wiki:PSC PSC]. Release managers are assumed to have permission to create a branch.
    8888
    89  * All source code in SVN should be in Unix [http://en.wikipedia.org/wiki/Newline text format] (LF) as opposed to DOS (CR+LF) or Mac OS text mode (CR).
     89 * All source code in Sgit should be in Unix [http://en.wikipedia.org/wiki/Newline text format] (LF) as opposed to DOS (CR+LF) or Mac OS text mode (CR).
    9090
    9191 * 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, Windows and Mac OS), 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.