Sheriffing/How To/Landing patches: Difference between revisions

Sheriffing/How To/Landing patches (view source)

39 bytes added , 24 February 2014

Few tweaks

canmove, Confirmed users

1,126

edits

@@ Line 4: / Line 4: @@
 * <u><b>Verify that the patch has proper review before doing anything else</b></u>
 ** [https://wiki.mozilla.org/Modules Module information]
-* Add the patch to the appropriate repository's queue via saving the attachment from the bug and using hg import or using a tool like bzexport to automate the process.
+* Add the patch to the appropriate repository's queue via saving the attachment from the bug and using hg import or using a tool like qimportbz to automate the process.
 ** For general core patches, land on mozilla-inbound.
 ** For core B2G work (*NOT* platform-independent core patches that happen to be fixing a B2G bug), use b2g-inbound.
-** For Firefox front-end work, use fx-team.
+** For Firefox front-end work/any Firefox for Android-specific work, use fx-team.
 * Apply the patch via qpush.
 * If the patch does not apply cleanly, you can look at the rejects and decide if the rebase is simple enough resolve yourself or you can remove the checkin-needed request and ask the developer to post an updated patch for checkin. <b>Don't forget to qrefresh after resolving conflicts!</b>