122
edits
Firefox/Go Faster/System Add-ons/Process: Difference between revisions
Firefox/Go Faster/System Add-ons/Process (view source)
Revision as of 16:45, 18 April 2017
, 18 April 2017Link to guidance on network requests, and note that RelMan is not responsible for cross-team coordination.
(→Verification of Test Channel: Specifics) |
(Link to guidance on network requests, and note that RelMan is not responsible for cross-team coordination.) |
||
| Line 15: | Line 15: | ||
The major use cases for system add-ons is to roll out a vetted and QA'd feature or fix off of the standard release trains. | The major use cases for system add-ons is to roll out a vetted and QA'd feature or fix off of the standard release trains. | ||
If you're thinking of [[Firefox/Making Network Requests From Firefox|Making Network Requests From Firefox]], there is specific guidance to follow. | |||
=== Are there development resources for system add-ons? === | === Are there development resources for system add-ons? === | ||
| Line 128: | Line 130: | ||
=== 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. | 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. | ||
'''Responsibility''': add-on developer; release management | '''Responsibility''': add-on developer; release management | ||