Sheriffing/How To/Landing patches: Difference between revisions

Jump to navigation Jump to search
Removed mention of mcMerge (not needed anymore, now done automatically)
No edit summary
(Removed mention of mcMerge (not needed anymore, now done automatically))
Line 19: Line 19:
*** Format should be something like "Bug 123456 - Add a null check to XYZ to avoid a crash. r=somebody"
*** Format should be something like "Bug 123456 - Add a null check to XYZ to avoid a crash. r=somebody"
* If a patch is missing commit information, remind the patch author to include it for future patches with a link to the [https://developer.mozilla.org/en-US/docs/Mercurial_FAQ#How_can_I_generate_a_patch_for_somebody_else_to_check-in_for_me.3F Mercurial FAQ page] that describes how to set it.
* If a patch is missing commit information, remind the patch author to include it for future patches with a link to the [https://developer.mozilla.org/en-US/docs/Mercurial_FAQ#How_can_I_generate_a_patch_for_somebody_else_to_check-in_for_me.3F Mercurial FAQ page] that describes how to set it.
* When the patches are applied cleanly and the commit information is correct, push to the appropriate integration branch and mark the bugs via mcMerge.
** mcMerge will clear the checkin-needed bug keyword. You will need to manually clear checkin-needed if on the whiteboard or set checkin+ if the checkin? patch flag is set.
Confirmed users
599

edits

Navigation menu