Add-ons/Hotfix: Difference between revisions
< Add-ons
Jump to navigation
Jump to search
(Keep cross-team deploy procedure separate from technical development details (but do interlink)) |
(add examples) |
||
| Line 6: | Line 6: | ||
== Deployment == | == Deployment == | ||
# The intent to ship a new hotfix needs to be notified to release-drivers@m.o and moc@m.c | # The intent to ship a new hotfix needs to be notified to release-drivers@m.o and moc@m.c ([https://mail.mozilla.org/private/release-drivers/2015-August/029924.html Example 1], [https://mail.mozilla.org/private/release-drivers/2015-September/030005.html Example 2] - Needs access to the r-d archives) | ||
# Bug is filed with the unsigned hotfix file attached. | # Bug is filed with the unsigned hotfix file attached ([https://bugzilla.mozilla.org/show_bug.cgi?id=1196000 Example 1], [https://bugzilla.mozilla.org/show_bug.cgi?id=1201065 Example 2]) | ||
# Bug is assigned to the Add-ons team for signing and staging. (:kmag or :jorgev, otherwise contact ammo-team@m.c) | # Bug is assigned to the Add-ons team for signing and staging. (:kmag or :jorgev, otherwise contact ammo-team@m.c) | ||
# File is signed and is attached to the bug. | # File is signed and is attached to the bug. | ||
Revision as of 13:42, 2 September 2015
The add-on hotfix is a tool used to ship changes to Firefox users that don't need to be distributed under the normal update mechanism. Examples of this are configuration changes that don't justify a point release, or changes that need to be pushed to users in older versions of Firefox.
Hotfix updates are automatically pushed to all Firefox users (starting from version 11).
This page contains the current procedure for deploying a hot fix. For technical details of coding a hot fix, please see [1].
Deployment
- The intent to ship a new hotfix needs to be notified to release-drivers@m.o and moc@m.c (Example 1, Example 2 - Needs access to the r-d archives)
- Bug is filed with the unsigned hotfix file attached (Example 1, Example 2)
- Bug is assigned to the Add-ons team for signing and staging. (:kmag or :jorgev, otherwise contact ammo-team@m.c)
- File is signed and is attached to the bug.
- Signed file is uploaded to addons.allizom.org and published.
- Bug is reassigned to QA for testing.
- QA signs off, hotfix owner signs off.
- Bug is reassigned to Add-ons team for final deployment.
- Add-ons team notifies release-drivers@m.o and moc@m.c about the deployment, including bug number.
- Signed file is uploaded to addons.mozilla.org and published.