New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 651690 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Oct 9
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Define change management procedures/guidelines

Project Member Reported by dsansome@chromium.org, Sep 30 2016

Issue description

From https://docs.google.com/document/d/1FkJqybVsYpVg4TT8u8VPNLDFmq8td-tkL3w_OVDLD2Y/edit?ts=57e514b1:

A "change management procedures" document will describe things like timing of changes, communication, arranging for others to be available during changes.

It doesn't have to be some heavy, oppressive Change Management system, but it would be useful to agree on a set of standard actions when performing various types of changes.

E.g.
low risk change -> "just do it"
high risk change -> "1) Send email to blah, 2) Don't do it at end of the day, 3) Test change on blah using blah, 4) Make sure blah is available in case something goes wrong""
 
Cc: benhenry@chromium.org
Components: -Infra Infra>Documentation
I'd like to help with this.
Status: WontFix (was: Assigned)
Stale bugs - closing

Sign in to add a comment