version 1.8, 2008/09/03 16:18:51
|
version 1.9, 2008/09/03 16:20:46
|
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. |
Line 45 binaries (not just the binaries in your |
|
Line 45 binaries (not just the binaries in your |
|
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 54 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. |