Release Management/Release Process Checklist Documentation: Difference between revisions

# Add a Release Tracking Sheet link to [https://wiki.mozilla.org/Release_Management/Release_owners Release Owners] wiki

#* Add the link to the date in the Release Date column.  

#* Note: This is performed on the Friday before Merge Day.

## Update the Release Milestones in Bugzilla

##* The products and milesontes are automatically completed

## Click [ Submit ]

## Edit the current cf_tracking_thunderbird_esr tracking flag to add the new release as a Value and deactivate the oldest release.

##* Example: If esr is based on 91, 95 is going to Release, 96 is going to Beta, and 97 is becoming the Nightly, then edit cf_tracking_firefox_esr91 to add a Value 97+ set to mozilla-next-drivers and deactivate the Value 94+.

# Create a release notes skeleton in [https://nucleus.mozilla.org/ Nucleus].

## Click '''Admin Interface'''

#** Check the possible commit in [https://github.com/mozilla/application-services application-services main] that corresponds to the failure.

#** Start a thread on [https://mozilla.slack.com/archives/C0559DDDPQF #application-services-eng] for investigation.

# Review the [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&f1=cf_tracking_firefox_relnote&o1=equals&v1=%3F&f2=cf_status_firefox138&o2=anywords&v2=affected%2Cfixed%2Cverified%2Cfix-optional&f3=cf_status_firefox138&o3=notsubstring&v3=disabled&title=Release%20Note%20Requests Release Notes requests] for Nightly tickets

#* These are nominated by setting the relnote flag to ?  for a particular release

#* Use the [https://matrix.to/#/#releaseduty:mozilla.org #releaseduty] channel on Matrix.

#* Align they are available for support if needed.

# Create checklist(s) for the new ESR cycle

#* Create a checklist for the relevant ESR that corresponds to the Firefox mainline release

#* Check the Beta simulations document for the release, this document is emailed to Release Management at the start of the night cycle.

#* Ensure that central does not currently have any known severe regressions or performance issues that would be carried into beta.

# Perform the [https://moz-releng-docs.readthedocs.io/en/latest/how-to/releaseduty/merge-duty/merge_duty.html#release-merge-day-part-ii-a-week-after-merge-day Release Merge Day - part II] steps

# Send the merge complete email to release-signoff and release-drivers

#* "The version bump to xxx has now landed on mozilla-central and the soft freeze period is over."

# application-services: Create an application-services release branch with the format release-vXXX off of the [https://github.com/mozilla/application-services/tree/main main branch]

# application-services: Create a new Application Services release in Ship-It

# application-services: Start the Application Services build in Ship-It via Promote

## See [https://github.com/mozilla/application-services/releases/tag/v132.0 example tag]

# application-services: Notify the application-services dev team on [https://mozilla.enterprise.slack.com/archives/C0559DDDPQF #application-services-eng] that the release branch is ready, the version bumped was merged, and the release is ready

# Switch to Application Services in Firefox Android to Release

#* Change the Version and Channel in mobile/android/android-components/plugins/dependencies/src/main/java/ApplicationServices.kt

# Turn on [https://support.google.com/googleplay/android-developer/answer/9859654?hl=en managed publishing] in the Play Console for Focus.

# Manually create a Focus release on the closed testing track (Foxfooding) @ 25% rollout and submit for review

#* Please Note: Desktop Build Validation sign-off is usually provided the day after Merge Day.

#* QA will post a message to the [https://mozilla.slack.com/archives/CAC9YSH3P #qa-coordination] channel in Slack when they complete functional testing.   

#* This allows the app to publish automatically once it passes review.

# Turn off managed publishing in the Play Console for Focus

# Verify the [https://product-details.mozilla.org/1.0/mobile_versions.json mobile_versions.json] is correct

#* Verify the beta_version is correct

#* Use the relevant beta macro

#* Please note: After all the beta steps are complete, the tab can be hidden in order to minimize clutter.

# Review tracking-firefoxXX+ bugs and approval requests.

#* This step is performed as part of the daily activities, tracked in the checklist for confirmation.

#* For b3+, once QA has signed off, roll out Focus to the Closed testing - Foxfooding track in Google Play to 100%.

#** Reply to the QA sign-off Slack message and include the rollout percentage.

==As available, the following items should be monitored during the Beta cycle==

# Go to [https://treeherder.mozilla.org/ Treeherder].

# Select the beta repo.

# Select “Custom push action…”

# Choose ''merge-automation'' from the dropdown.

<pre>force-dry-run: false

behavior: early-to-late-beta

</pre>

After the job runs, verify that the commit was pushed to the mozilla-beta repo, see [https://hg.mozilla.org/releases/mozilla-beta/rev/29e6215562511ffef7bfa73bed97093ec3d8cdd4 example].

==The following needs to be performed at the end of the Beta Cycle==

# Disable automated beta builds in Ship-it.

# Please Note: Monitor beta/release uplift requests between the final beta build and the beta to release merge. It is possible that a late uplift request may come in for a regression/stability fix, evaluate if this is a blocker for the RC and if it should be uplifted to beta before the beta to release merge and RC build.

=RC Checklist=

## Connect to the VPN.

## Log into [https://shipit.mozilla-releng.net/ Ship-It].

## Complete as follows and click Create Release:

##* [[File:Screen Shot 2022-06-07 at 9.26.10 AM.png|thumb|center]]

# Turn on managed publishing in the Play Console for Fenix/Focus/Klar.

# Manually create a Fenix/Focus/Klar release on the Production track with a 5% rollout.

# Push Desktop to Beta at 100% from Ship-It via Ship RC.

#* [[File:Screenshot 2022-06-07 at 09-32-46 RelMan Activities Overview.png|thumb|center]]

## Submit to the store for review

#* Please see [https://docs.microsoft.com/en-us/windows/uwp/publish/app-submissions App submissions] documentation for additional information on the Microsoft Store submission process.

==As available, the following should be monitored/performed during RC week for Desktop/Android==

#* Reply to the QA sign-off slack message

#** “Thanks, pushed to Production at 5% rolled out.

=RC Uplifts=

# Verify that security advisories are live [https://www.mozilla.org/en-US/security/advisories/ here]

# Verify that the [https://partner.microsoft.com/en-us/dashboard/products/9NZVDKPMR9RD/overview Microsoft Store] is published at 25% rollout

#* See [https://github.com/mozilla-releng/releasewarrior-2.0/blob/master/docs/release-promotion/desktop/ubuntu-snap.md#promote-a-snap-to-the-stable-channel Promote a snap to the stable channel] for more information

# Send Slack message to [https://mozilla.slack.com/archives/C6HD6P4TF #release-coordination] to notify of the release

# Bump the [https://partner.microsoft.com/en-us/dashboard/products/9NZVDKPMR9RD/overview Microsoft Store] rollout to 100%.

#* Click Finalize package rollout

# Review fenix/focus release crash rates, incoming bugs for new blockers, and spike/trend in negative play store reviews.

#* Check to see if there is anything concerning that would prevent completing the rollout.

# Update the Weekly Digest document, as requested on [https://mozilla.slack.com/archives/C01TTHGPSKB #fx-weekly-digest].

#* Update the Release Milestones (Details) section to add status on the release, dot release, etc.

##* If an app is still pending review on a closed track then you cannot promote it to a production track.

##* See [https://support.google.com/googleplay/android-developer/answer/9859348?hl=en Prepare and roll out a release] for more information.

##* Keep the same release notes as the major release. Add any new notes at the top prefixed by the dot release version.

##* With managed publishing turned on, the app will not automatically release after the store review.

# Follow the same process as monitoring when an RC build has QA sign-off with the following exceptions:

## Turn off [https://support.google.com/googleplay/android-developer/answer/9859654?hl=en managed publishing] in the Play Console.