Tree Rules/Integration: Difference between revisions

Tree Rules/Integration (view source)

27 bytes removed , 8 July 2014

m

→‎Sheriff Duty: Clarify notification process

canmove, Confirmed users

1,126

edits

@@ Line 34: / Line 34: @@
 * Sheriffs will watch this tree and back out bustage/regressions as necessary to keep it green.
 ** Bustage is backed out right away. There's no "we'll let you fix this tree while everybody stands by".
-** The backout will be noted in the bug. Sheriffs need only email developers about the backout outside of Bugzilla if specifically requested in the bug (developers who do not read all bugmail are encouraged to set up appropriate mail filters on bugs to which they are assigned, to ensure they are aware of the backout).
+** The backout will be noted in the bug. The onus isn't on the sheriff to contact the developer via IRC regarding the backout. Developers who do not read all bugmail are encouraged to set up appropriate mail filters on bugs to which they are assigned, to ensure they are aware of the backout.
 ** If it's not possible to identify the guilty changeset, the sheriffs may backout more changesets to minimize the overhead/time to fix the tree. Completely innocent pushes will be relanded by the sheriff once the bustage is cleared or, in case of doubts, a Try server run will be requested in the bug, before the next landing.
 ** See ehsan's blogpost on how to [http://ehsanakhgari.org/blog/2010-09-09/backing-out-multiple-consecutive-changesets-mercurial back out multiple consecutive changesets], or mak's [https://wiki.mozilla.org/User:Mak77 backout shell script] or Sfink's [https://bitbucket.org/sfink/qbackout qbackout Hg extension].