Firefox/Go Faster/System Add-ons/Process: Difference between revisions

← Older edit

Firefox/Go Faster/System Add-ons/Process (view source)

Revision as of 17:27, 23 April 2019

728 bytes added , 23 April 2019

m

→‎Deployment Bug, Intent to Ship and RelMan Approval

Rdalal

Confirmed users

18

edits

@@ Line 101: / Line 101: @@
 '''Responsibility''': add-on developer/owner; code reviewer; QA
-= Intent to Ship and RelMan Approval =
+= Deployment Bug, Intent to Ship and RelMan Approval =
+=== Deployment Bug ===
+Once the add-on has been reviewed by QA, a [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=System%20Add-ons%3A%20Off-train%20Deployment deployment bug should be filed] under the "System Add-ons: Off-train Deployment" component.
+This bug should mark the tracking bug as a dependency. Additionally the bug should have the XPI file attached.
+A sample bug can be found here: https://bugzilla.mozilla.org/show_bug.cgi?id=1546450
 === Intent to Ship ===
-Once the add-on has been reviewed by QA, an Intent to Ship email should be sent.
+After filing the deployment bug, an Intent to Ship email should be sent.
 Please expect a lead time of at least 3 business days between the email being sent, and the add-on released into production. Holidays and work weeks will effect scheduling.
@@ Line 112: / Line 119: @@
 |-
 ! Field !! Example
+|-
+| Deployment bug || filed under the System Add-ons: Off-train Deployment component
 |-
 | Tracking bug || see Getting Started for samples
@@ Line 136: / Line 145: @@
 === Release Management Approval ===
-The driver of the current release should Reply All to the Intent to Ship email with approval for release. Note that Release Management Approval does not necessarily all stakeholders are of aware of your add-on's effects. If you might impact other teams, be sure to contact them as well.
+The driver of the current release should Reply All to the Intent to Ship email with approval for release. In addition they should sign off in the deployment bug. Please request that they do so.
+Note that Release Management Approval does not necessarily all stakeholders are of aware of your add-on's effects. If you might impact other teams, be sure to contact them as well.
 '''Responsibility''': add-on developer; release management
@@ Line 168: / Line 179: @@
 The purpose of this step is to receive verification that the add-on is being deployed correctly on the test channel (`release-sysaddon`).
-This will be done by the QA team (as of this writing, RyanVM's team).
+This will be done by the QA team.
 Notes on how best to verify system add-ons on the test channel can be found here: https://wiki.mozilla.org/Firefox/Go_Faster/Releasing_an_add-on_mechanics#Verifying_Balrog
@@ Line 183: / Line 194: @@
 Example: https://bugzilla.mozilla.org/show_bug.cgi?id=1312528#c19
+Once the rules have been updated in Balrog, the changes must be sign off by Relman/Releng.
 Update Deployment Matrix: https://docs.google.com/spreadsheets/d/1yOgiOTU8q2I709VFhjCYCLATmoyQueV8RttPzciFIkQ/edit#gid=0
-'''Responsibility''': Go Faster Team
+'''Responsibility''': Go Faster Team, Relman/Releng
 = Measurement =
 Q4 Goal is to track rollout of the add-on. See: https://wiki.mozilla.org/Firefox/Go_Faster/Measurement