Introduction
So you have a tagged released version of GlastRelease, and we desire to update this released version with tweaks, patches, and updated packages.
Updating the affected package(s)
Currently, all packages used by GR are automatically branched when GR is tagged. The branch naming convention is: GlastReleasevirjpk
See the workbook discussion concerning branches:
Performing the update to GlastRelease
Checkout the GlastReleasevirjpk branch of GlastRelease:
cvs co -rGlastReleasevirjpk GlastRelease
Update the GlastRelease requirements file to use the new tag(s)
cvs ci -m"log message"
Triggering a build
The ReleaseManager currently ignores updates along the branches so no HEAD buid will start. However, we can trigger them manually.
System Tests
It is recommended that systests be performed on the new GR branch HEAD before officially tagging the branch.
Tagging Convention
The "p" portion of the tag will be reserved for the case where we are updating GR along a branch.