canmove, Confirmed users
725
edits
Inbound Sheriff Duty: Difference between revisions
Jump to navigation
Jump to search
→What are the tree rules for mozilla-inbound?
| Line 2: | Line 2: | ||
* Committers are not required to actively watch this tree | * Committers are not required to actively watch this tree | ||
* Bugs remain open until the changeset makes it to m-c. | * Bugs remain open until the changeset makes it to m-c. | ||
** Optionally add "[inbound]" to the status whiteboard for bugs that have been fixed on mozilla-inbound. | |||
* The Sheriff will watch this tree and back out bustage/regressions as necessary to keep mozilla-inbound green | * The Sheriff will watch this tree and back out bustage/regressions as necessary to keep mozilla-inbound green | ||
* Bustage is backed out right away. There's no "we'll let you fix this tree while everybody stands by". | * Bustage is backed out right away. There's no "we'll let you fix this tree while everybody stands by". | ||
| Line 8: | Line 9: | ||
** 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] | ** 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] | ||
* Once or more a day, the sheriff will merge a green -inbound changeset to -central | * Once or more a day, the sheriff will merge a green -inbound changeset to -central | ||
** Resolve bugs that were landed, set appropriate target milestone. | |||
== Who manages mozilla-inbound? == | == Who manages mozilla-inbound? == | ||