Confirmed users, Bureaucrats and Sysops emeriti
1,081
edits
IT/ChangeControl: Difference between revisions
→CAB Approval Process
| Line 45: | Line 45: | ||
==Submitting a Change Request== | ==Submitting a Change Request== | ||
= CAB Approval Process= | |||
== Informational Only == | |||
Information Only Approvals can be granted for limited-scope changes for things where you have blanket approval. | Information Only Approvals can be granted for limited-scope changes for things where you have blanket approval. | ||
Example: Some changes may be pre-approved as part of a larger project. These CAB requests are merely information that "we are doing this upgrade". It is not necesssary to wait for an approval; a veto may be issued if there are extenuating circumstances. | Example: Some changes may be pre-approved as part of a larger project. These CAB requests are merely information that "we are doing this upgrade". It is not necesssary to wait for an approval; a veto may be issued if there are extenuating circumstances. | ||
== 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. | 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. | 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 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. | 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. | ||
| Line 64: | Line 64: | ||
* Pending (require contingencies for the Requester to fullfill (shifting start time, improved rollout/rollback plans). | * Pending (require contingencies for the Requester to fullfill (shifting start time, improved rollout/rollback plans). | ||
== 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. | 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. | ||