The software comprising the pipeline and what it runs is under configuration control for the remainder of the GLAST Beam test period. After baselining the code, all modifications to the running code will need to be approved by the Change Control Board. The purpose of configuration control is to understand the code content that affects processing results, and to maximize system uptime by vetting changes that affect reliability.
CCB Actions List
Proposed changes will be recorded in the CCB with an explanation of the need, changes and consequences. These will be recorded in blogs in this confluence space. We will start off by requiring documentation of the new state of the pipeline and results of systems tests.
The need should be recorded in JIRA issues, with a trail through to resolution of the issue.
The software under control is the pipeline itself (database, pipeline code and user interfaces) and all scripts and executables run by the pipeline. This includes online, svac and SAS code.
Inclusion of the tagged packages will be proposed to the gatekeeper (Michael Kuss) who will prepare new releases. These are based on tested GlastRelease releases as much as possible. System tests will be run.
The svac scripts and pipeline front and back ends are more procedural pieces, not affecting the results; only the operability of the system.