CVS Tat Format
The format of an LCLS Software Release CVS tag is <module_name>R<X><Y>-<Z>, where
X is the major version number
Y is the minor version number
Z is the micro version number.
The parameters Y and Z start at zero, while the X parameter starts at 1. Therefore the first release would be <modulename>-R1-0-0.
For packages maintained off-site, "-lcls#" will be attached to the tag, where # starts at 1 and increases as the build for that package changes internally at SLAC. For instance, ipac which is a package maintained at APS, has a vendor tag from Andrew Johnson of 2.8 would be tagged inititally at SLAC with ipac-R2-8-lcls1. When this package is changed onsite, for instance built with a new version of rtems, the new tag woudl be ipac-R2-8-lcls2, and so on.
Module Contents
Each modules at SLAC must contain the following files at TOP
If a package is imported from offsite, and does not contain these files, the local module maintainer will add these files to CVS. The file RELEASE_SITE, will be included in the configure/RELEASE file, and should include the following variable path definitions:
EPICS_BASE=/afs/lsac/g/lcls/epics
EPICS_MODULES=/afs/slac/g/lcls/modules
EPICS_EXTENSIONS/afs/slac/g/lcls/extensions
The version of base, modules and extensions will be defined within the configure/RELEASE file.
Currently, the RELEASE_SITE file is included in CVS and modified manually. However, in future this file will be generated automatically and the contents of RELEASE_SITE will be populated based on environment variables set by the users.
