Add-ons/Hotfix: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Added note about hotfix updates)
(Minor changes to replace "handed off" with "reassigned" and add the r-d and moc aliases.)
Line 5: Line 5:
== Deployment ==
== Deployment ==
# Bug is filed with the unsigned hotfix file attached.
# Bug is filed with the unsigned hotfix file attached.
# Bus is handed off to the Build & Release team for signing.
# Bus is assigned 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 for staging (normally :jorgev, otherwise contact ammo-team@m.c).
# Bug is re-assgiend 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 reassigned to QA for testing.
# QA signs off, hotfix owner signs off.
# QA signs off, hotfix owner signs off.
# Bug is handed off to Add-ons team.
# Bug is reassigned to Add-ons team for final deployment.
# Add-ons team notify release-drivers and moc about upcoming hotfix release.
# Add-ons team notifies release-drivers@mozilla.org and moc@mozilla.com about the deployment.
# Signed file is uploaded to addons.mozilla.org and published.
# Signed file is uploaded to addons.mozilla.org and published.

Revision as of 14:47, 12 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.

Hotfix updates are automatically pushed to all Firefox users (starting from version 11).

Deployment

  1. Bug is filed with the unsigned hotfix file attached.
  2. Bus is assigned to the Build & Release team for signing.
  3. File is signed and is attached to the bug.
  4. Bug is re-assgiend 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 reassigned to QA for testing.
  7. QA signs off, hotfix owner signs off.
  8. Bug is reassigned to Add-ons team for final deployment.
  9. Add-ons team notifies release-drivers@mozilla.org and moc@mozilla.com about the deployment.
  10. Signed file is uploaded to addons.mozilla.org and published.