Add-ons/Hotfix: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(update contact info)
No edit summary
Line 10: Line 10:
# QA signs off, hotfix owner signs off.
# QA signs off, hotfix owner signs off.
# Bug is handed off to Add-ons team.
# Bug is handed off to Add-ons team.
# Add-ons team notify release-drivers AND moc about upcoming hotfix release.
# Add-ons team notify release-drivers and moc about upcoming hotfix release.
# Signed file is uploaded to addons.mozilla.org and published.
# Signed file is uploaded to addons.mozilla.org and published.

Revision as of 21:40, 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

  1. Bug is filed with the unsigned hotfix file attached.
  2. Bus is handed off to the Build & Release team for signing.
  3. File is signed and is attached to the bug.
  4. Bug is handed off to Add-ons team for staging (normally :jorgev, otherwise contact ammo-team@m.c).
  5. Signed file is uploaded to addons-dev.allizom.org and published.
  6. Bug is handed off to QA for testing.
  7. QA signs off, hotfix owner signs off.
  8. Bug is handed off to Add-ons team.
  9. Add-ons team notify release-drivers and moc about upcoming hotfix release.
  10. Signed file is uploaded to addons.mozilla.org and published.