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

m
Line 101: Line 101:
'''Responsibility''': add-on developer/owner; code reviewer; QA
'''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]. This bug should mark the tracking bug as a dependency.


=== Intent to Ship ===  
=== 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.
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 115:
|-
|-
! Field !! Example
! Field !! Example
|-
| Deployment bug || filed under the System Add-ons: Off-train Deployment component
|-
|-
| Tracking bug || see Getting Started for samples
| Tracking bug || see Getting Started for samples
Line 136: Line 141:
=== Release Management Approval ===
=== 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
'''Responsibility''': add-on developer; release management
Confirmed users
18

edits