Sheriffing/Deciding To Close A Tree: Difference between revisions

Sheriffing/Deciding To Close A Tree (view source)

11 bytes removed , 19 July 2017

no edit summary

canmove, Confirmed users

2,850

edits

Revision as of 23:09, 19 July 2017 (view source) ChrisCooper (talk \| contribs) No edit summary ← Older edit		Revision as of 23:12, 19 July 2017 (view source) ChrisCooper (talk \| contribs) No edit summary Newer edit →
Line 37:		Line 37:
	In the event of longer tree closures, you may hit the end of your workday. If this happens, or better still, before it happens, find someone who can continue acting overseeing the tree closure. If you've followed all the above steps, there should be an adequate papertrail for someone to follow and continue.		In the event of longer tree closures, you may hit the end of your workday. If this happens, or better still, before it happens, find someone who can continue acting overseeing the tree closure. If you've followed all the above steps, there should be an adequate papertrail for someone to follow and continue.

	Note: in the event of more systemic failures, e.g. major infrastructure failures or AWS outages, it is best to ~~invoke the~~ [[~~https~~:~~//mana.mozilla.org/wiki/display/MOC~~ MOC]] (Mozilla Operations Center, #moc on IRC). They have 24/7 support and ~~are well-versed in similar process to the above~~.		Note: in the event of more systemic failures, e.g. major infrastructure failures or AWS outages, it is best to [[Sheriffing/How:To:Escalate\|escalate the issue to the MOC]] (Mozilla Operations Center, #moc on IRC). They have 24/7 support and much experience dealing with outages.