2 Tags are symbolic name of the repository content at a specific
5 We put tags on each release. Currently we have tags on:
7 * PsN-2_2_5-rc1. Bugfixes an features on the way to 2.2.5
8 * PsN-2_2_4-stable, this is the released 2.2.4. And thus the
9 point most branches are created from.
11 * PsN-2_2_4 (OBSOLETE, see above)
12 * Various tags related to branching and merging between
13 patches and serial. At the time of writing (14/11 -
14 07). They could largely be ignored. The important tags are
15 on 2_2_4 described above.
16 * PsN-2.2.0 called PsN_2_2_0
18 Tags are created like this:
22 Allways (!) from the top CVS directory and to avoid confusion,
23 make sure all your changes are checked in. Though you don't
24 necessarily need to have run "cvs update".
28 Branches are copies of the repository used for patching releases.
30 We create branches when a release needs patching. Currently we have a branch on
32 * PsN-2.2.4 called PsN-2_2_4-patches (from tag PsN-2_2_4-stable)
33 * PsN-2.2.4 called PsN-2_2_4-experimental (Will become PsN-3.0)
34 * PsN-2.2.0 called PsN-2_2_0_patches_serial (now merged with MAIN)
35 * PsN-2.2.0 called PsN-2_2_0_patches_serial (This one is a spelling error OBSOLETE)
36 * PsN-2.2.0 called PsN_2_2_0-patches
37 * PsN-2.1.10 called PsN-2-1-10
38 * PsN-2.1.9 called PsN-2-1-9
39 * PsN-2.1.5 called PsN-2-1-5 (This branch differs from the release!, I consider it obsolete/PP)
40 * release-2.1.1 ( I don't know what this is, consider it obsolete /PP )
42 Branches are created like this:
44 * cvs rtag -b -r PsN_2_2_0 PsN_2_2_0-patches PsN
46 PsN_2_2_0 is the tag used to branch from. Thus you must create
47 a tag first. PsN_2_2_0-patches is the name of the tag. PsN is
50 To change a branch, you must first check it out (It will create a new directory called "PsN" be carefull!!)
52 * cvs -z9 -d :ext:pontus_pih@psn.cvs.sourceforge.net:/cvsroot/psn co -r PsN-2-1-10 PsN
54 Then change what you need and commit as usual. If you make a release, make sure to tag it!