Mercurial > p > roundup > code
comparison doc/developers.txt @ 4228:f5d7562bed95
update to dev docs
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Mon, 20 Jul 2009 23:26:10 +0000 |
| parents | be9122d753c5 |
| children | 8d3582271a99 |
comparison
equal
deleted
inserted
replaced
| 4226:d0a3ac73b4c1 | 4228:f5d7562bed95 |
|---|---|
| 20 - roundup-dev mailing list at | 20 - roundup-dev mailing list at |
| 21 http://lists.sourceforge.net/mailman/listinfo/roundup-devel | 21 http://lists.sourceforge.net/mailman/listinfo/roundup-devel |
| 22 - Sourceforge's issue trackers at | 22 - Sourceforge's issue trackers at |
| 23 https://sourceforge.net/tracker/?group_id=31577 | 23 https://sourceforge.net/tracker/?group_id=31577 |
| 24 | 24 |
| 25 Website, wiki, issue tracker | |
| 26 ---------------------------- | |
| 27 | |
| 28 1. Log into <username>,roundup@shell.sourceforge.net | |
| 29 2. cd /home/groups/r/ro/roundup | |
| 30 3. follow instructions in README.txt | |
| 31 | |
| 32 | |
| 25 Small Changes | 33 Small Changes |
| 26 ------------- | 34 ------------- |
| 27 | 35 |
| 28 Most small changes can be submitted through the `feature tracker`_, with | 36 Most small changes can be submitted through the `feature tracker`_, with |
| 29 patches attached that give context diffs of the affected source. | 37 patches attached that give context diffs of the affected source. |
| 30 | 38 |
| 31 | 39 |
| 32 CVS Access | 40 SVN Access |
| 33 ---------- | 41 ---------- |
| 34 | 42 |
| 35 To get CVS access, contact richard@users.sourceforge.net. | 43 To get SVN access, contact richard@users.sourceforge.net. |
| 36 | 44 |
| 37 CVS stuff: | |
| 38 | |
| 39 1. to tag a release (eg. the pre-release of 0.5.0):: | |
| 40 | |
| 41 cvs tag release-0-5-0-pr1 | |
| 42 | |
| 43 1. to make a branch (eg. branching for code freeze/release):: | |
| 44 | |
| 45 cvs co -d maint-0-5 -r release-0-5-0-pr1 roundup | |
| 46 cd maint-0-5 | |
| 47 cvs tag -b maint-0-5 | |
| 48 | |
| 49 2. to check out a branch (eg. the maintenance branch for 0.5.x):: | |
| 50 | |
| 51 cvs co -d maint-0-5 -r maint-0-5 | |
| 52 | |
| 53 3. to merge changes from the maintenance branch to the trunk, in the | |
| 54 directory containing the HEAD checkout:: | |
| 55 | |
| 56 cvs up -j maint-0-5 | |
| 57 | |
| 58 though this is highly discouraged, as it generally creates a whole swag | |
| 59 of conflicts :( | |
| 60 | |
| 61 Standard tag names: | |
| 62 | |
| 63 *release-maj-min-patch[-sub]* | |
| 64 Release of the major.minor.patch release, possibly a beta or pre-release, | |
| 65 in which case *sub* will be one of "b*N*" or "pr*N*". | |
| 66 *maint-maj-min* | |
| 67 Maintenance branch for the major.minor release. Patch releases are tagged in | |
| 68 this branch. | |
| 69 | |
| 70 Typically, release happen like this: | |
| 71 | |
| 72 1. work progresses in the HEAD branch until milestones are met, | |
| 73 2. a series of beta releases are tagged in the HEAD until the code is | |
| 74 stable enough to freeze, | |
| 75 3. the pre-release is tagged in the HEAD, with the resultant code branched | |
| 76 to the maintenance branch for that release, | |
| 77 4. bugs in the release are patched in the maintenance branch, and the final | |
| 78 and patch releases are tagged there, and | |
| 79 5. further major work happens in the HEAD. | |
| 80 | 45 |
| 81 Project Rules | 46 Project Rules |
| 82 ------------- | 47 ------------- |
| 83 | 48 |
| 84 Mostly the project follows Guido's Style (though naming tends to be a little | 49 Mostly the project follows Guido's Style (though naming tends to be a little |