Add-ons/Hotfix: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(add deprecation notice for signing)
Line 4: Line 4:


== Deployment ==
== Deployment ==
<font color='red'>'''This sequence is out of date since {{bug|1151537}} - responsibility for signing has shifted away from Build & Release. {{bug|1161311}} implies it belongs to Cloud Services now.'''</font>
# 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
# Bug is filed with the unsigned hotfix file attached.
# Bug is filed with the unsigned hotfix file attached.
# Bug is assigned to the Build & Release team for signing. (Ping in #releng or email release@m.c if urgent.)
# Bug is assigned to the Add-ons team for signing. (:kmag or :jorgev)
# File is signed and is attached to the bug.
# 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).
# Bug is re-assigned to Add-ons team for staging (normally :jorgev, otherwise contact ammo-team@m.c).

Revision as of 16:29, 10 August 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).

Deployment

  1. The intent to ship a new hotfix needs to be notified to release-drivers@m.o and moc@m.c
  2. Bug is filed with the unsigned hotfix file attached.
  3. Bug is assigned to the Add-ons team for signing. (:kmag or :jorgev)
  4. File is signed and is attached to the bug.
  5. Bug is re-assigned to Add-ons team for staging (normally :jorgev, otherwise contact ammo-team@m.c).
  6. Signed file is uploaded to addons-dev.allizom.org and published.
  7. Bug is reassigned to QA for testing.
  8. QA signs off, hotfix owner signs off.
  9. Bug is reassigned to Add-ons team for final deployment.
  10. Add-ons team notifies release-drivers@m.o and moc@m.c about the deployment, including bug number.
  11. Signed file is uploaded to addons.mozilla.org and published.