See bug 1181153. date, time, duration of maintenance Flexible, but preferred: Thursday 10/1 at 6am US/Pacific Duration: about 2 hours system(s) affected https://treestatus.mozilla.org end-user impact Planned impact: inability for sheriffs to change tree status during transition Potential impact: tree closure due to failure of the service during transition (transition is designed to avoid this possibility) maintenance plan and timeline (link to a wiki or etherpad is fine) https://etherpad.mozilla.org/treestatus-migration rollback plan / rollback point (at which point will you determine to roll back) If the initial deployment causes a try push to fail, we can revert back to the initial state. notification mechanisms Initial: * blog post * email to release@, sheriffs@ * post to dev.tree-management * direct contact for affected parties During transition: #developers who will be point, who else will be involved Dustin; will require someone from webops to disable the pingdom alert before beginning.
Update per conversation with :atoll -- let's do this during the next TCW.
Reviewed by CAB 9/30 - Approved for 10/10 TCW
Flags: cab-review? → cab-review+
We did this before the TCW
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.