Compatibility/System Addon/Override Policies and Workflows: Difference between revisions

Jump to navigation Jump to search
m (→‎Checklist for shipping a site patch: Update Bugzilla product/component link)
Line 22: Line 22:
# Once the site patch is validated locally and given an r+, the PR should get merged.
# Once the site patch is validated locally and given an r+, the PR should get merged.
# A patch should be generated against Mozilla Central in order to release a new version of the Go Faster addon, following [https://github.com/mozilla/webcompat-addon#exporting-the-sources-to-mozilla-central these instructions], including a minor version bump.
# A patch should be generated against Mozilla Central in order to release a new version of the Go Faster addon, following [https://github.com/mozilla/webcompat-addon#exporting-the-sources-to-mozilla-central these instructions], including a minor version bump.
# The patch should be attached to the bug in Step 2 and a [[Modules/All#Firefox|Firefox module peer]] must give an r+ for landing.
# The patch should be attached to the bug in Step 2 and a [[Modules/All#WebCompat_Addons|WebCompat Addons module peer]] must give an r+ for landing.
# A signed XPI built from the r+ patch for deploying should be attached to the bug in Step 2. See the [[Firefox/Go_Faster/System_Add-ons/Process#QA_and_Code_Review|Go Faster Process Document]] for further info.
# A signed XPI built from the r+ patch for deploying should be attached to the bug in Step 2. See the [[Firefox/Go_Faster/System_Add-ons/Process#QA_and_Code_Review|Go Faster Process Document]] for further info.
# A [https://mana.mozilla.org/wiki/display/PI/PI+Request PI Request] should be sent linking to the XPI for testing against the site being patched.
# A [https://mana.mozilla.org/wiki/display/PI/PI+Request PI Request] should be sent linking to the XPI for testing against the site being patched.
Confirmed users
796

edits

Navigation menu