Version: | 1.6 |
---|
Note: the intended audience of this document is the developers of the core Roundup code. If you just wish to alter some behaviour of your Roundup installation, see customising roundup.
Anyone wishing to help in the development of Roundup must read Roundup's Design Document and the implementation notes.
All development is coordinated through two resources:
Most small changes can be submitted through the Feature tracker, with patches attached that give context diffs of the affected source.
To get CVS access, contact richard@users.sourceforge.net.
CVS stuff:
to tag a release (eg. the pre-release of 0.5.0):
cvs tag release-0-5-0-pr1
to make a branch (eg. branching for code freeze/release):
cvs co -d maint-0-5 -r release-0-5-0-pr1 cd maint-0-5 cvs tag -b maint-0-5
to check out a branch (eg. the maintenance branch for 0.5.x):
cvs co -d maint-0-5 -r maint-0-5
to merge changes from the maintenance branch to the trunk, in the directory containing the HEAD checkout:
cvs up -j maint-0-5
though this is highly discouraged, as it generally creates a whole swag of conflicts :(
Standard tag names:
Typically, release happen like this:
Mostly the project follows Guido's Style (though naming tends to be a little relaxed sometimes). In short:
Other project rules:
The administrators of the project reserve the right to boot developers who consistently check in code which is either broken or takes the codebase in directions that have not been agreed to.
Back to Table of Contents