...
Proposed changes will be submitted to the CCB with an explanation of the need, changes and consequences. These will be recorded in blogs (labeled sassoccb) in this confluence space. Approval will be recorded here also. Consideration and approval may be done via email, vrvs evo meeting or phone depending on the urgency of the request. We will start off by requiring unanimous approval from the board members for the action to be approved.
...
The software under control is the pipeline itself (database, pipeline code and user interfaces) and all scripts and executables run by the pipeline for Level 1 processing and ASP. This includes Science Ops and SAS code.
Once we have approved the request internally, we will forward it to the Mission Office, where a 24 hour turnaround is promised. The request will be made with this form.
GlastRelease package
A tagged release of GlastRelease will form the core of reconstruction code run in the pipeline. Changes to this release would be performed on a branch in cvs. Inclusion of the tagged packages will be proposed to the gatekeeper (Heather Kelly) who will prepare new releases. These are based on tested GlastRelease releases as much as possible. System tests will be run. There should be an Science Ops meeting presentation demonstrating the evidence - system tests plus jira issues. Indviduals should represent their changes at these meetings (note: this did not work in I&T!)
...