Inbound Sheriff Duty: Difference between revisions

→‎What are the tree rules for mozilla-inbound?: Clarification around extra info needed if multiple patches + emphasise no longer using [inbound] in whiteboard
m (Requesting that try links (if there are any) are added when pushing to m-i)
(→‎What are the tree rules for mozilla-inbound?: Clarification around extra info needed if multiple patches + emphasise no longer using [inbound] in whiteboard)
Line 18: Line 18:
*Bugs remain open until the changeset makes it to m-c.  
*Bugs remain open until the changeset makes it to m-c.  
*When landing on inbound, please make the following bug state changes, to save time for the people doing the merges:
*When landing on inbound, please make the following bug state changes, to save time for the people doing the merges:
**Add the inbound changeset URL to the bug.  
**Add the inbound changeset URL to the bug. NB: If there are multiple patches on the bug, please indicate which one the changeset is for (eg: use patch -> details -> comment on patch).
**If the bug should remain open after the inbound changeset makes it to mozilla-central (eg patches left to land or other work needs doing), please indicate this in the whiteboard.
**Set the target milestone.
**Set the target milestone.
**Check the assignee, platform, in-testsuite flag & other fields are correctly set.
**Check the assignee, platform, in-testsuite flag & other fields are correctly set.
**If this has been sent to try, please include the URL, so in the case of mozilla-inbound bustage, it's easier to eliminate your push as the cause.
**If this has been sent to try, please include the URL, so in the case of mozilla-inbound bustage, it's easier to eliminate your push as the cause.
**<strike>Optionally add "[inbound]" to the status whiteboard for bugs that have been fixed on mozilla-inbound.</strike> Means the merges take even longer - and not done consistently anyway, so better to just use the inbound changeset URL comment as indication of being of inbound instead.  
**<strike>Optionally add "[inbound]" to the status whiteboard for bugs that have been fixed on mozilla-inbound.</strike> '''Please do not do this any more''', as it means the merges take even longer - and was not being done consistently anyway, so better to just use the inbound changeset URL comment as indication of landing on inbound instead.  
*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".  
canmove, Confirmed users
1,126

edits