version 1.8, 2008/09/03 16:18:51
|
version 1.12, 2009/07/29 21:25:44
|
Line 18 should be of the form: |
|
Line 18 should be of the form: |
|
#define jsoc_version "V3R5" | #define jsoc_version "V3R5" |
#define jsoc_vers_num (305) | #define jsoc_vers_num (305) |
| |
4. From the machine used in step 2, commit $JSOCROOT/base/libdrms/jsoc_version.h. |
4. From the machine used in step 2, commit $JSOCROOT/base/jsoc_version.h. |
| |
5. Add a new file, JSOC/CM/V<MAJ>.<MIN>/release.notes. This has the | 5. Add a new file, JSOC/CM/V<MAJ>.<MIN>/release.notes. This has the |
release notes (see below). Commit. | release notes (see below). Commit. |
| |
6. From the machine used in step 2, create a tag for the new release. | 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 | 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 | version numbers in place ("V3R5" and "305" in this example). Ensure |
that the tag was successfully created and create actual release | that the tag was successfully created and create actual release |
binaries (not just the binaries in your sandbox). Login as the 'jsoc' | binaries (not just the binaries in your sandbox). Login as the 'jsoc' |
user, cd to /home/jsoc/cvs, and do "cvs checkout -r Ver_<MAJ>-<MIN> | user, cd to /home/jsoc/cvs, and do "cvs checkout -r Ver_<MAJ>-<MIN> |
JSOC" and build on all machines supported. | JSOC" and build on all machines supported. |
| |
9. Once again, edit $JSOCROOT/base/libdrms/jsoc_version.h. The |
9. Once again, edit $JSOCROOT/base/jsoc_version.h. The |
version macros should be of the form: | version macros should be of the form: |
| |
#define jsoc_version "V3R5X" | #define jsoc_version "V3R5X" |
Line 54 version macros should be of the form: |
|
Line 61 version macros should be of the form: |
|
The "X" and "-" denote that binaries were created from non-release code. | The "X" and "-" denote that binaries were created from non-release code. |
| |
10. From the machine used in step 9, commit | 10. From the machine used in step 9, commit |
$JSOCROOT/base/libdrms/jsoc_version.h. You might have to run "cvs |
$JSOCROOT/base/jsoc_version.h. You might have to run "cvs |
update -A base/libdrms/jsoc_version.h" to clear the sticky flag created |
update -A base/jsoc_version.h" to clear the sticky flag created |
when you first sync'd in step 2 (if you used the "-r" flag). | when you first sync'd in step 2 (if you used the "-r" flag). |
| |
11. Send instructions for using the new release to users. | 11. Send instructions for using the new release to users. |