...
Quick Links
Process
Proposed changes will be submitted to the CCB with an explanation of the need, changes and consequences. These can be recorded in blogs (aka "news item", labeled sassoccb) in any space, if desired. Otherwise the content can appear entirely in jira itself. Approval will be recorded here also. Consideration and approval may be done via email, 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.
...
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!)
...
The board is composed of Richard Dubois (chair), Eduardo do Couto e Silva , Bill AtwoodSteve Ritz, Rob Cameron, Analysis Coordinator (Julie McEneryNicola Omodei), C&A Lead (as needed; Luca Latronico and Philippe Bruel). email traffic for the board can be viewed here. Nicola Omodei will act as CCB chair in Richard's absence.