Mercurial > p > roundup > code
comparison doc/developers.txt @ 1244:8dd4f736370b
merge from maintenance branch
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Thu, 03 Oct 2002 06:56:30 +0000 |
| parents | 43ab730ee194 |
| children | 7d8ab32fc829 |
comparison
equal
deleted
inserted
replaced
| 1243:3a028d2f7830 | 1244:8dd4f736370b |
|---|---|
| 1 ================== | 1 ================== |
| 2 Developing Roundup | 2 Developing Roundup |
| 3 ================== | 3 ================== |
| 4 | 4 |
| 5 :Version: $Revision: 1.4 $ | 5 :Version: $Revision: 1.5 $ |
| 6 | 6 |
| 7 Note: the intended audience of this document is the developers of the core | 7 Note: the intended audience of this document is the developers of the core |
| 8 Roundup code. If you just wish to alter some behaviour of your Roundup | 8 Roundup code. If you just wish to alter some behaviour of your Roundup |
| 9 installation, see `customising roundup`_. | 9 installation, see `customising roundup`_. |
| 10 | 10 |
| 33 CVS Access | 33 CVS Access |
| 34 ---------- | 34 ---------- |
| 35 | 35 |
| 36 To get CVS access, contact richard@users.sourceforge.net. | 36 To get CVS access, contact richard@users.sourceforge.net. |
| 37 | 37 |
| 38 CVS stuff: | |
| 39 | |
| 40 1. to tag a release (eg. the pre-release of 0.5.0):: | |
| 41 | |
| 42 cvs tag release-0-5-0-pr1 | |
| 43 | |
| 44 1. to make a branch (eg. branching for code freeze/release):: | |
| 45 | |
| 46 cvs co -d maint-0-5 -r release-0-5-0-pr1 | |
| 47 cd maint-0-5 | |
| 48 cvs tag -b maint-0-5 | |
| 49 | |
| 50 2. to check out a branch (eg. the maintenance branch for 0.5.x):: | |
| 51 | |
| 52 cvs co -d maint-0-5 -r maint-0-5 | |
| 53 | |
| 54 3. to merge changes from the maintenance branch to the trunk, in the | |
| 55 directory containing the HEAD checkout:: | |
| 56 | |
| 57 cvs up -j maint-0-5 | |
| 58 | |
| 59 Standard tag names: | |
| 60 | |
| 61 *release-maj-min-patch[-sub]* | |
| 62 Release of the major.minor.patch release, possibly a beta or pre-release, | |
| 63 in which case *sub* will be one of "b*N*" or "pr*N*". | |
| 64 *maint-maj-min* | |
| 65 Maintenance branch for the major.minor release. Patch releases are tagged in | |
| 66 this branch. | |
| 67 | |
| 68 Typically, release happen like this: | |
| 69 | |
| 70 1. work progresses in the HEAD branch until milestones are met, | |
| 71 2. a series of beta releases are tagged in the HEAD until the code is | |
| 72 stable enough to freeze, | |
| 73 3. the pre-release is tagged in the HEAD, with the resultant code branched | |
| 74 to the maintenance branch for that release, | |
| 75 4. bugs in the release are patched in the maintenance branch, and the final | |
| 76 and patch releases are tagged there, and | |
| 77 5. further major work happens in the HEAD. | |
| 38 | 78 |
| 39 Project Rules | 79 Project Rules |
| 40 ------------- | 80 ------------- |
| 41 | 81 |
| 42 Mostly the project follows Guido's Style (though naming tends to be a little | 82 Mostly the project follows Guido's Style (though naming tends to be a little |