Add-ons/Hotfix: Difference between revisions

Jump to navigation Jump to search
m
→‎Deployment: added clarifications and note to have separate bug for the signed file
(add examples)
m (→‎Deployment: added clarifications and note to have separate bug for the signed file)
Line 6: Line 6:


== Deployment ==
== Deployment ==
# The intent to ship a new hotfix needs to be notified to release-drivers@m.o and moc@m.c ([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 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 assigned to the Add-ons team for signing and staging. (:kmag or :jorgev, otherwise contact ammo-team@m.c)
# 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)
# File is signed and is attached to the bug.
# File is signed and is attached to the signing bug.
# Signed file is uploaded to addons.allizom.org and published.
# Signed file is uploaded to addons.allizom.org and published.
# Bug is reassigned to QA for testing.
# Bug is reassigned to QA for testing.
Confirmed users
2,816

edits

Navigation menu