From: richard Date: Mon, 20 Jul 2009 23:26:10 +0000 (+0000) Subject: update to dev docs X-Git-Url: https://git.tokkee.org/?a=commitdiff_plain;h=7417a6c0e8382104a7dce6e53b511f684fd496ca;p=roundup.git update to dev docs git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/roundup/trunk@4333 57a73879-2fb5-44c3-a270-3262357dd7e2 --- diff --git a/doc/developers.txt b/doc/developers.txt index fd5b16f..6698616 100644 --- a/doc/developers.txt +++ b/doc/developers.txt @@ -22,6 +22,14 @@ All development is coordinated through two resources: - Sourceforge's issue trackers at https://sourceforge.net/tracker/?group_id=31577 +Website, wiki, issue tracker +---------------------------- + +1. Log into ,roundup@shell.sourceforge.net +2. cd /home/groups/r/ro/roundup +3. follow instructions in README.txt + + Small Changes ------------- @@ -29,54 +37,11 @@ Most small changes can be submitted through the `feature tracker`_, with patches attached that give context diffs of the affected source. -CVS Access +SVN Access ---------- -To get CVS access, contact richard@users.sourceforge.net. - -CVS stuff: - -1. to tag a release (eg. the pre-release of 0.5.0):: - - cvs tag release-0-5-0-pr1 - -1. to make a branch (eg. branching for code freeze/release):: - - cvs co -d maint-0-5 -r release-0-5-0-pr1 roundup - cd maint-0-5 - cvs tag -b maint-0-5 - -2. to check out a branch (eg. the maintenance branch for 0.5.x):: - - cvs co -d maint-0-5 -r maint-0-5 - -3. 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: - -*release-maj-min-patch[-sub]* - Release of the major.minor.patch release, possibly a beta or pre-release, - in which case *sub* will be one of "b*N*" or "pr*N*". -*maint-maj-min* - Maintenance branch for the major.minor release. Patch releases are tagged in - this branch. - -Typically, release happen like this: +To get SVN access, contact richard@users.sourceforge.net. -1. work progresses in the HEAD branch until milestones are met, -2. a series of beta releases are tagged in the HEAD until the code is - stable enough to freeze, -3. the pre-release is tagged in the HEAD, with the resultant code branched - to the maintenance branch for that release, -4. bugs in the release are patched in the maintenance branch, and the final - and patch releases are tagged there, and -5. further major work happens in the HEAD. Project Rules -------------