Confirmed users, Bureaucrats and Sysops emeriti
1,081
edits
IT/ChangeControl: Difference between revisions
Jump to navigation
Jump to search
→CAB Approval Process
| Line 52: | Line 52: | ||
=== Minor Changes === | === Minor Changes === | ||
Minor Changes needed limited approval because they are limited in scope and shouldn't hold up for a long time waiting for the next meeting. These Changes require a single CAB member signoff where there's little to no risk and/or impact limited to known scope. | |||
Approved Minor Changes are to be reported at the next CAB Meeting but the CAB Member who approved the Minor Change. | |||
=== Major Changes === | === Major Changes === | ||
Major Changes require the board in quorum. The Change Requester (or proxy) will be invited to the CAB Meeting to defend the request/change. Undefended requests will be deferred. | |||
The CAB will mark the Request: | |||
* will never approved | |||
* Approved | |||
* Pending (require contingencies for the Requester to fullfill (shifting start time, improved rollout/rollback plans). | |||
=== Emergency Changes === | === Emergency Changes === | ||
Emergency/breakfix changes will be handled on an as-needed basis with the primary purpose focused on restoring service. These changes require no pre-authorization. | |||
Mozilla SRE will inform the CAB via email with a short description of the change and the reason for it. | |||
Mozilla SRE will attend the next CAB Meeting to walk through Root Cause Analysis. | |||