Release Management/Process coordination for handling off-train releases: Difference between revisions

m
added section for remote settings
m (added section for remote settings)
 
(10 intermediate revisions by 3 users not shown)
Line 8: Line 8:


The list of off-train release requests include (but are not limited to):
The list of off-train release requests include (but are not limited to):
* Shipping content via Remote Settings
* Shipping a new Mozilla webextension
* Shipping a new Mozilla webextension
* [https://wiki.mozilla.org/Firefox/Go_Faster/System_Add-ons/Process GoFaster] for shipping new system add-ons
* [https://wiki.mozilla.org/Firefox/Go_Faster/System_Add-ons/Process GoFaster] for shipping new system add-ons
Line 38: Line 39:
| align=center| '''Checklist'''
| align=center| '''Checklist'''
|- style="border:1pt solid #000000;padding:0.176cm;"
|- style="border:1pt solid #000000;padding:0.176cm;"
| align=center| Content sent via Remote Settings
|| Publishing content to Firefox users with the in-product messaging system (Remote Settings)
''Example:'' (TBD)
<u>Typical time-to-ship</u>: (TBD)
|| Product manager/Dev owner files a bug and adds the messaging-system-request flag, filling out the resulting Bugzilla comment form.
<u>Driver</u>: Product owner
|| ✅ Product owner
✅ Publishing engineer
✅ Messaging (Firefox) Engineering peer
✅ Messaging Product owner
✅ Relman owner
||[https://docs.google.com/document/d/1TAu5OQ_hWZjfL4k9-b7uEcjjyvWhgeQQD6X5ksCC7bc/edit#heading=h.rfqkfzwwckon Messaging system intake and release process]
|- style="border:1pt solid #000000;padding:0.176cm;"
| align=center| New Mozilla webext
| align=center| New Mozilla webext
|| A business need to publish Mozilla owned webext to Firefox Desktop users via AMO.
|| A business need to publish Mozilla owned webext to Firefox Desktop users via AMO.
Line 59: Line 84:




|| TODO add a link to a template for the process
||  
|- style="border:1pt solid #000000;padding:0.176cm;"
|- style="border:1pt solid #000000;padding:0.176cm;"
| align=center| GoFaster
| align=center| GoFaster
Line 212: Line 237:
= General process =
= General process =


As all these processes are similar, the general process is describe. Specificities are described in dedicated checklists.
As all these processes are similar, the general process is described. Specific details are described in dedicated checklists.


# Kick-off email thread or meeting to establish scope, owners and timeline.
# Kick-off email thread or meeting to establish scope, owners and timeline.
Line 226: Line 251:
# Publication of the change
# Publication of the change
# QA sign off of the publication of the change
# QA sign off of the publication of the change
= Process: Messaging to users with Remote Settings =
==Decisions==
== Extra steps ==
== Checklist ==
== Extra information ==
[https://docs.google.com/document/d/1eDDIZCp_pD01cCeghum7fLRDqmEl3dfds9y3yI4W9Hw/edit Messaging system intake and release process]


= Process: Shipping a New Mozilla Webextension =
= Process: Shipping a New Mozilla Webextension =
Line 429: Line 465:


== Extra information ==
== Extra information ==
The steps for shipping a system add-on are described in detail here:


[https://wiki.mozilla.org/Firefox/Go_Faster/System_Add-ons/Process https://wiki.mozilla.org/Firefox/Go_Faster/System_Add-ons/Process]
[https://wiki.mozilla.org/Firefox/Go_Faster/System_Add-ons/Process https://wiki.mozilla.org/Firefox/Go_Faster/System_Add-ons/Process]
Line 608: Line 645:


# In Experimenter, after you have completed your "Draft", click the "[https://mana.mozilla.org/wiki/display/FIREFOX/Pref-Flip+and+Add-On+Experiments#Pref-FlipandAdd-OnExperiments-ReadyforSign-offs Ready for Sign-offs]" button to get the checklist of Required and Optional items needed to launch your study.
# In Experimenter, after you have completed your "Draft", click the "[https://mana.mozilla.org/wiki/display/FIREFOX/Pref-Flip+and+Add-On+Experiments#Pref-FlipandAdd-OnExperiments-ReadyforSign-offs Ready for Sign-offs]" button to get the checklist of Required and Optional items needed to launch your study.
# When you have all your required and optional checklist items complete, click the "Ready to Ship" button to let Normandy know this is ready to be launched.  You will be contacted with any questions.


== Checklists ==
== Checklists ==
Line 659: Line 697:


Useful links
Useful links
* [https://docs.google.com/document/d/1MQKsT1pNR30Qtc6B7a_1egcnOt7ft-fJhelrQZUrre8/edit?usp=sharing Release management risk assessment criteria]  
* [https://mana.mozilla.org/wiki/display/FIREFOX/Pref-Flip+and+Add-On+Experiments#Pref-FlipandAdd-OnExperiments-Risks&Testing risk assessment criteria]  
* [https://wiki.mozilla.org/Firefox/Shield/Shield_Studies https://wiki.mozilla.org/Firefox/Shield/Shield_Studies]
* [https://mana.mozilla.org/wiki/display/FIREFOX/Pref-Flip+and+Add-On+Experiments#Pref-FlipandAdd-OnExperiments-GettingStarted Experimenter Guidance]


= Process: Feature rollout via Normandy =
= Process: Feature rollout via Normandy =
Line 669: Line 707:


== Decisions ==
== Decisions ==
* Timeline
* Timeline (Refer to the [https://docs.google.com/document/d/1xiWjGqK-s3NiqEY-Qg34eAm1Nca5iqzEUE8udRX1ku0/edit feature rollout playbook] for help with this)
* Products affected: Desktop, Fennec, ESR?
* Products affected: Desktop, Fennec, ESR?
* Platforms affected: All, Windows, Mac, Linux?
* Platforms affected: All, Windows, Mac, Linux?
Line 676: Line 714:


== Extra steps ==
== Extra steps ==
# File a bug for handling the rollout (example: {{bug|1467514}})
# File a bug for handling the rollout (examples: {{bug|1467514}} or {{bug|1523978}})
# Development owner (likely mythmon) configures the recipe in Normandy to flip pref for targeted end-users
# Development owner (likely mythmon) configures the recipe in Normandy to flip pref for targeted end-users
# For release-unblockers/hotfixes, set up on stage, so QA can test on https://delivery-console.stage.mozaws.net
# Release owner reviews, approves and publishes recipe
# Release owner reviews, approves and publishes recipe
# Feature team, release owner monitor data to verify:
# Feature team, release owner monitor data to verify:
Confirmed users
2,816

edits