Tree Rules/Integration: Difference between revisions

Jump to navigation Jump to search
m
→‎Please do the following after pushing to inbound: Clarify the whiteboard string to stop bug being closed on merge, so that any future automated script has something consistent to work with
m (→‎Sheriff Duty: English grammar/usage tweaks)
m (→‎Please do the following after pushing to inbound: Clarify the whiteboard string to stop bug being closed on merge, so that any future automated script has something consistent to work with)
Line 28: Line 28:
* <strike>Optionally add "[inbound]" to the status whiteboard for bugs that have been fixed on mozilla-inbound.</strike>
* <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. Just leave the inbound changeset in a comment on the bug instead.
** '''Please do not do this any more''', as it means the merges take even longer - and was not being done consistently anyway. Just leave the inbound changeset in a comment on the bug instead.
* If the bug should remain open after the inbound changeset makes it to mozilla-central (e.g. patches left to land or other work needs doing), leave a note in the status whiteboard.
* If the bug should remain open after the inbound changeset makes it to mozilla-central (e.g. patches left to land or other work needs doing), please add "[Leave open after merge]" to the bug whiteboard.
* If you backout from inbound, annotate that in the bug. This helps sheriffs when merging.
* If you backout from inbound, annotate that in the bug. This helps sheriffs when merging.


canmove, Confirmed users
1,126

edits

Navigation menu