Add-ons/Hotfix: Difference between revisions
< Add-ons
Jump to navigation
Jump to search
m (Added moc) |
No edit summary |
||
| Line 1: | Line 1: | ||
The add-on hotfix is a tool used to ship changes to Firefox users that | 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). | Hotfix updates are automatically pushed to all Firefox users (starting from version 11). | ||
Revision as of 20:06, 12 December 2014
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).
Deployment
- The intent to ship a new hotfix needs to be notified to release-drivers@m.o and moc@m.c
- Bug is filed with the unsigned hotfix file attached.
- Bug is assigned to the Build & Release team for signing.
- File is signed and is attached to the bug.
- Bug is re-assigned to Add-ons team for staging (normally :jorgev, otherwise contact ammo-team@m.c).
- Signed file is uploaded to addons-dev.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.