...
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 any space. 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.
Notification of change requests should be emailed to the CCB email list, and should include the url of the request news item. Once the request for a change has been made, a JIRA issue will be opened up in the SSC project to track the request.
Here is the recipe:
- requestor creates a Jira item in the SSC project, leaving the state as "In Preparation"
- once it is ready to go, the requestor selects Submit to SAS-SO CCB from the workflow. This puts it in the hands of the CCB.
- the CCB determines the "severity" of the request (whether to send to the LAT &/or and Mission CCBs) and changes the priority on the issue.
- Then the issue is routed to the approriate next CCB or approved (or rejected)
- if a minor issue, and approved then the LAT CCB is notified of the change
- if approved, the issue is assigned back to the requestor, who sets the issue to "Implemented", and then closes the issue or the CCB folks do.
The request should cover the need for the change; the fix; how it was tested; and how it can be backed outThe 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 for Halfpipe and Level 1 processing and ASP. This includes Science Ops and SAS code.
...