canmove, Confirmed users
2,850
edits
ReleaseEngineering:Buildduty:Downtimes: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering:Buildduty:Downtimes (view source)
Revision as of 23:54, 16 January 2012
, 16 January 2012→Who do I notify, and when?
ChrisCooper (talk | contribs) (Created page with "==How do I schedule a downtime?== Whenever RelEng/IT/WebDev wants a tree-closing downtime for work on any systems, they should contact the RelEng BuildDuty person of the day in ...") |
ChrisCooper (talk | contribs) |
||
| Line 54: | Line 54: | ||
# etherpad/email everyone who will be working in the downtime, and ask to approve the draft downtime notice | # etherpad/email everyone who will be working in the downtime, and ask to approve the draft downtime notice | ||
# '''BEFORE''' posting to the newsgroups, send draft copy of the downtime notice to the list of pre-approvers. Ask for any objections/questions. | # '''BEFORE''' posting to the newsgroups, send draft copy of the downtime notice to the list of pre-approvers. Ask for any objections/questions. | ||
# post the downtime notice to the dev.planning | # post the downtime notice to the '''dev.planning''' & '''dev.tree-management''' newsgroups, and send a copy of the notice to '''all@m.c'''. | ||
# err on the side of over-communication, i.e. play it safe: if you think a group will be impacted by a downtime and they are not included in the lists above, contact them. | # err on the side of over-communication, i.e. play it safe: if you think a group will be impacted by a downtime and they are not included in the lists above, contact them. | ||
# All of the above notifications should go out *at least 24 hours* before the planned downtime. | # All of the above notifications should go out *at least 24 hours* before the planned downtime. | ||