Inbound Sheriff Duty: Difference between revisions

Jump to navigation Jump to search
m
→‎After landing on mozilla-inbound: Improve heading/intro wording
(Move list of changes people should be making to bugs, to its own section)
m (→‎After landing on mozilla-inbound: Improve heading/intro wording)
Line 25: Line 25:
*Push to mozilla-inbound like any special branch, that is, it is recommended to have a separate local tree. Pull to it, apply your patches, and then push to mozilla-inbound.
*Push to mozilla-inbound like any special branch, that is, it is recommended to have a separate local tree. Pull to it, apply your patches, and then push to mozilla-inbound.


== After landing on mozilla-inbound ==
== Please do the following after landing on mozilla-inbound ==


After landing on inbound, please make the following bug state changes, to save time for the people doing the merges:
In order to save time for the people doing the merges, after pushing to inbound please:
*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).
*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).
*Set the target milestone.
*Set the target milestone.
canmove, Confirmed users
1,126

edits

Navigation menu