Add-ons/Hotfix: Difference between revisions

Jump to navigation Jump to search
→‎Deployment: Don't sign random XPI's attached to bugs. Sign what's in VCS which requires review and Level 3
(→‎Deployment: Don't sign random XPI's attached to bugs. Sign what's in VCS which requires review and Level 3)
Line 66: Line 66:
== Deployment ==
== Deployment ==
# The intent to ship a new hotfix needs to be sent to release-drivers@m.o and moc@m.c by the developer, by a release manager, or by someone from the AMMO team ([https://mail.mozilla.org/private/release-drivers/2015-August/029924.html Example 1], [https://mail.mozilla.org/private/release-drivers/2015-September/030005.html Example 2] - Needs access to the r-d archives)
# The intent to ship a new hotfix needs to be sent to release-drivers@m.o and moc@m.c by the developer, by a release manager, or by someone from the AMMO team ([https://mail.mozilla.org/private/release-drivers/2015-August/029924.html Example 1], [https://mail.mozilla.org/private/release-drivers/2015-September/030005.html Example 2] - Needs access to the r-d archives)
# Bug is filed with the unsigned hotfix file attached ([https://bugzilla.mozilla.org/show_bug.cgi?id=1196000 Example 1], [https://bugzilla.mozilla.org/show_bug.cgi?id=1201065 Example 2])
# Bug is filed   ([https://bugzilla.mozilla.org/show_bug.cgi?id=1244321 Example 1], [https://bugzilla.mozilla.org/show_bug.cgi?id=1237209 Example 2])
# Clone the bug into a new bug, and assign it to the Add-ons team for signing and staging. (:kmag or :jorgev, otherwise contact the AMMO team, ammo-team@m.c) ([https://bugzilla.mozilla.org/show_bug.cgi?id=1196078 Example 1], [https://bugzilla.mozilla.org/show_bug.cgi?id=1201129 Example 2])
# File a new bug in addons.mozilla.org::Administration, and assign it to the Add-ons team for signing and staging. (:kmag or :jorgev, otherwise contact the AMMO team, ammo-team@m.c) ([https://bugzilla.mozilla.org/show_bug.cgi?id=1196078 Example 1], [https://bugzilla.mozilla.org/show_bug.cgi?id=1201129 Example 2]) with the following instructions (replace vYYYYMMDD.NN with the hotfix version):
#:To generate the hotfix XPI, do the following:
#: <br/>
#:hg clone https://hg.mozilla.org/releases/firefox-hotfixes
#:cd firefox-hotfixes
#:HOTFIX=vYYYYMMDD.NN make package
#: <br/>
#:Then sign the xpi generated at build/hotfix-vYYYYMMDD.NN.xpi
#: <br/>
#:Please deploy to addons-dev.allizom.org for QA
# File is signed and is attached to the signing bug.
# File is signed and is attached to the signing bug.
# Signed file is uploaded to addons-dev.allizom.org and published.
# Signed file is uploaded to [https://addons-dev.allizom.org/firefox/addon/firefox-hotfix/ addons-dev.allizom.org] and published.
# Bug is reassigned 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 reassigned to Add-ons team for final deployment.
# 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.
# 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.
# Signed file is uploaded to [https://addons.mozilla.org/firefox/addon/firefox-hotfix/ addons.mozilla.org] and published.
Confirmed users
933

edits

Navigation menu