canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,334
edits
Sheriffing/Sheriff Duty: Difference between revisions
→When should I reopen the tree after closing it?
(add sections on when to close/open the tree) |
|||
| Line 32: | Line 32: | ||
== When should I reopen the tree after closing it? == | == When should I reopen the tree after closing it? == | ||
When the tree has been closed due to build bustage, performance regressions, or test regressions, it should be reopened once: | |||
* the sheriff has confidence that those regressions are diagnosed and being fixed (preferably fixed already), and | |||
* tinderbox is clear enough (or expected to be in the cycle that current checkins would go into) that any new regressions that should be caught will be. | |||
This does not mean that all boxes need to cycle green again before reopening. However, if there were a large number of checkins since things started going bad, it is often good to wait for test boxes to cycle green again to make sure there aren't regressions in what has already landed. | |||
If there has been a lot of tree closure recently, continuing to hold the tree closed increases the chances that there will be a mess when it reopens and everybody lands at once. Tree closures should therefore be kept to the minimum necessary, especially when there have been many recent closures or there is an upcoming deadline. | |||
== How do I open/close the mozilla tree? == | == How do I open/close the mozilla tree? == | ||