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

||  

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

= Process: Messaging to users with Remote Settings =

* Products supported: Desktop / Fennec / both

* Platforms supported

* Firefox versions supported

* Release readiness criteria

** QA  

** Performance

** Security review

* What kind of telemetry data will this webext capture and send to Mozilla?

* Timeline and rollout strategy

* Is GoFaster the [https://wiki.mozilla.org/Firefox/Go_Faster/When_To_Use_System_Add-ons appropriate release strategy]?

* By nature, the rest of the decisions are the same as a Mozilla Webextension

== Checklists ==

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

* Timeline

* Team

* Scope

* New User population that will be targeted

* Release readiness criteria

** QA

** Perf

** Security review

** Data & Privacy review

# Intent to ship email to release-drivers with the bug number

# Releng owner to configure balrog rules and sign offs

# Intent to ship email to release-drivers to explain the change

# The change should be published on the relevant platform

Shield studies are controlled A/B tests, using either a pref-flip or an add-on. They are available on all channels, namely Nightly, Beta, Release. A/B experiments are done to understand user behavior, user retention, onboarding, test feature ideas, etc.  

* Work with Data Science first to determine the best way to answer your questions.  A pref-flip or add-on study is only one way to find answers.  Guidance to get started with Data Science is [https://mana.mozilla.org/wiki/display/PM/Firefox+Data+Science#FirefoxDataScience-projectworkflow here]. 

* If Data Science and product determine a pref-flip or add-ons study is needed, you will fill out Experimenter together to get started. Getting Started guidance [https://mana.mozilla.org/wiki/display/FIREFOX/Pref-Flip+and+Add-On+Experiments#Pref-FlipandAdd-OnExperiments-GettingStarted here].  

* These are the [https://mana.mozilla.org/wiki/display/FIREFOX/Pref-Flip+and+Add-On+Experiments#Pref-FlipandAdd-OnExperiments-Stages stages] between starting Experimenter and the study releasing.

# 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.

| align=center| Data Science Bug

| align=center| product-owner

| align=center| Analysis Battery

| align=center| data scientist

| align=center| Experimenter Draft

| align=center| product-owner & data scientist

| align=center| Complete Study checklist

| align=center| product-owner

| align=center| Kick-off the study

| align=center| Normandy-owner

| align=center| Study Results

| align=center| product-owner & data scientist

Useful links

* [https://mana.mozilla.org/wiki/display/FIREFOX/Pref-Flip+and+Add-On+Experiments#Pref-FlipandAdd-OnExperiments-Risks&Testing risk assessment criteria]  

* [https://mana.mozilla.org/wiki/display/FIREFOX/Pref-Flip+and+Add-On+Experiments#Pref-FlipandAdd-OnExperiments-GettingStarted Experimenter Guidance]

* 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?

* Platforms affected: All, Windows, Mac, Linux?

* Rollout strategy

# 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

# 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

# Feature team, release owner monitor data to verify:

## Recipe uptake is going as planned

## Feature is having the intended effect on end-users

Dot release builds are pushed to release and/or ESR end-user users to mitigate release blocking issues.

* Timeline</div>

* Bugs that are dot release drivers and ride-alongs

* Products affected: Desktop, Fennec, ESR?

* Platforms affected: All, Windows, Mac, Linux?

* Rollout strategy

* Release notes, sec advisories, comms plan, What’s New Page

# Release owner drafts release notes and shares for review.

# Security owner drafts security advisory as needed and shares for review.

Example: [https://drive.google.com/open?id=1LTuQzvudGchDPELJkhpv7C8H7-2qTcmTvDokkZGpoFY 59.0.x dot release checklist]

* Timeline

* Products affected: Desktop, Fennec, ESR?

* Platforms affected: All, Windows, Mac, Linux?

* sec advisories, comms plan

# Security owner drafts security advisory as needed and shares for review.

# Create a CVE if necessary

# Reach out to partners and/or other projects impacted if needed

[https://docs.google.com/document/d/1SwiR6Jk9Sdqfd0CU06Qci0XlJ3fnoD6BGVkL1imrcgY/edit?usp=sharing Chemspill process description]