IT/ChangeControl: Difference between revisions

IT/ChangeControl (view source)

670 bytes removed , 15 August 2012

Confirmed users, Bureaucrats and Sysops emeriti

1,081

edits

@@ Line 44: / Line 44: @@
 It is the responsibility of the Change Advisory Board to implement a change control process that will provide management of all actions and modifications that may affect the stability of any production network, system, or service.
-The six steps for the Change Control Process will be followed when any modification is required within the production environment:
-# Planning
-# Testing
-# Approval
-# Communications
-# Executing the Change
-# Documentation
 ==Submitting a Change Request==
-Proposed changes need to be submitted by Monday EOB Pacific time using the following Bugzilla form <font color=red><b>need form</b></font>.
 == CAB Approval Process==
-The CAB will follow the following process to approve change work:
-* Stakeholders will add an "approved" comment in the bug
-* The CAB chairperson will use the <tt>cab-approved</tt> flag to indicate this work has been approved
-* The CAB chairperson will indicate this work has been schedule in the whiteboard