JSOC/CM/release.howto - diff

Return to release.howto CVS log

Up to [Development] / JSOC / CM

version 1.9, 2008/09/03 16:20:46

version 1.12, 2009/07/29 21:25:44

Line 24 should be of the form:

release notes (see below). Commit.

6. From the machine used in step 2, create a tag for the new release.

cd to $JSOCROOT. Run "cvs tag -c Ver_<MAJ>-<MIN> ." Replace <MAJ>

a. cd $JSOCROOT

with the major version number and <MIN> with the minor version number.

b. cvs tag -c Ver_<MAJ>-<MIN> . (Replace <MAJ>

with the major version number and <MIN> with the minor version number.)

c. cvs tag -d Ver_LATEST .

d. cvs tag -c Ver_LATEST .

7. The NetDRMS release version number should also be incremented and

tagged. Do "cvs checkout -r Ver_<MAJ>-<MIN> DRMS" followed by "cd

tagged:

$JSOCROOT; cvs tag -c NetDRMS_Ver_<MAJ>-<MIN>".

a. cd /tmp

b. cvs checkout NETDRMSONLY (head version of netdrms-only files)

c. cd JSOC

d. cvs tag -c NetDRMS_Ver_<MAJ>-<MIN> .

e. cvs tag -d Ver_DRMSLATEST .

f. cvs tag -c Ver_DRMSLATEST .

g. cd /tmp

h. cvs checkout -r Ver_<MAJ>-<MIN> CORE

i. cd JSOC

j. cvs tag -c NetDRMS_Ver_<MAJ>-<MIN> . (minus excluded files)

k. cvs tag -d Ver_DRMSLATEST .

l. cvs tag -c Ver_DRMSLATEST . (minus excluded files)

8. Update the "Ver_LATEST" tag. This tag always points to the latest

8. Now you must build all release executables with the release jsoc

release. "cvs tag -d Ver_LATEST .; cd $JSOCROOT; cvs rtag -r

Ver_<MAJ>-<MIN> Ver_LATEST JSOC", where <MAJ> and <MIN> are the

current release. Alternatively, try "cvs tag -d Ver_LATEST .; cd

tempdir; cvs checkout -r Ver_<MAJ>-<MIN> JSOC" followed by "cvs tag -c

Ver_LATEST".

9. Now you must build all release executables with the release jsoc

version numbers in place ("V3R5" and "305" in this example). Ensure

that the tag was successfully created and create actual release

binaries (not just the binaries in your sandbox). Login as the 'jsoc'

Legend: