Sheriffing/Sheriff Duty: Difference between revisions

Sheriffing/Sheriff Duty (view source)

608 bytes removed , 21 August 2012

Adjust instructions now that we've switched to treestatus

canmove, Confirmed users

1,126

edits

@@ Line 46: / Line 46: @@
 ** If it's a performance or unit test regression, the bug should say which tinderboxes, when, and give an URL to the list checkins that may have caused the regression.
 ** If it's a functional regression, the bug should have steps to reproduce, the dates of the nightly builds immediately surrounding the regression (or narrower window if known), and an URL to the list of checkins that could have caused the regression.
-* Update the tinderbox status message:
+* See https://wiki.mozilla.org/ReleaseEngineering/How_To/Close_or_Open_the_Tree
-** You'll need the [https://bugzilla.mozilla.org/show_bug.cgi?id=sheriffpass sheriff password]. Ask in #developers if you need access to it.
-** Go to [http://tinderbox.mozilla.org/admintree.cgi?tree=Firefox admintree.cgi]. This link is also at the bottom of the [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox tinderbox page].
-** Look in the "Status Message" textbox for instructions which begin <pre><!-- CURRENT TREE STATUS --></pre>
-** When closing, include the reason for the closure (if for something other than red/orange, this should include a hyperlink to the bug).
-** When opening the tree, remove the message added when closing.
 * Update the [http://wiki.mozilla.org/Tree_Closures tree closure log]