Add-ons/Hotfix: Difference between revisions
< Add-ons
Jump to navigation
Jump to search
(Setting up a basic page about the hotfix with a deployment list) |
(update contact info) |
||
| Line 5: | Line 5: | ||
# Bus is handed off to the Build & Release team for signing. | # Bus is handed off to the Build & Release team for signing. | ||
# File is signed and is attached to the bug. | # File is signed and is attached to the bug. | ||
# Bug is handed off to Add-ons team (normally :jorgev) | # Bug is handed off 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. | # Signed file is uploaded to addons-dev.allizom.org and published. | ||
# Bug is handed off to QA for testing. | # Bug is handed off to QA for testing. | ||
Revision as of 21:39, 10 December 2014
The add-on hotfix is a tool used to ship changes to Firefox users that can't 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.
Deployment
- Bug is filed with the unsigned hotfix file attached.
- Bus is handed off to the Build & Release team for signing.
- File is signed and is attached to the bug.
- Bug is handed off 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 handed off to QA for testing.
- QA signs off, hotfix owner signs off.
- Bug is handed off to Add-ons team.
- Add-ons team notify release-drivers AND moc about upcoming hotfix release.
- Signed file is uploaded to addons.mozilla.org and published.