Changes between Initial Version and Version 1 of CommitPolicy


Ignore:
Timestamp:
Nov 22, 2005, 7:02:23 PM (16 years ago)
Author:
Dominic Hargreaves
Comment:

initial portion. To complete.

Legend:

Unmodified
Added
Removed
Modified
  • CommitPolicy

    v1 v1  
     1== Openguides commit policy ==
     2
     3In order to ensure that OpenGuides development happens in a controlled way and with peer review, the following points need to be adhered to when contributing code (this is especially true for people with direct commit access to [wiki:Subversion Subversion], but also relevant for those submitting patches via the mailing list or Trac.
     4
     5=== Code style ===
     6
     7==== Indentation ====
     8
     9Follow the existing indentation style which is 4 spaces. Literal tabs are not used in OpenGuides development (if you are using vim, the following in your ~/.vimrc may help:
     10
     11{{{
     12set tabstop=4
     13set expandtab
     14}}}
     15
     16=== Before committing ===
     17
     18Before committing changes to the repository, you should ensure that all tests continue to pass (and if you have added more code, that you include new tests for it). If you're adding a new feature it's probably best to have discussed things first on the dev mailing list or on an enhancement ticket within Trac. You should most probably have an open ticket for the issue in any case.
     19
     20=== When to commit ===
     21
     22Sometimes the release manager will call the tree frozen to allow a release to happen. '''No''' changes to the tree should be made when the tree is frozen except by the release manager. I intend freeze points to be shown on the Trac roadmap.
     23
     24=== How to commit ===
     25