Closed Bug 1475315 Opened 8 years ago Closed 7 years ago

finalize process and incident command system for when treeclosures happen

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jlund, Unassigned)

Details

This is about taking the documentation of what we have for how to handle treeclosures. We should finalize and identify the following: * how unplanned and planned closures differ * what are the steps we do every time. e.g. file, update #ci, identify escalation path, etc * detail the various ways we categorize a closure. This is for reporting and postmortem purposes. It would be good to start getting an idea of what causes a closure and how often those situations happen * detail how and when we do postmortems * identify the role separation and communication expectations between ciduty, sheriffs, and moc. There is probably more here but this is a start.

Looking over the document, it looks pretty spot on!
Should we close this bug?

Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.