Release Management/Release Process Checklist Documentation: Difference between revisions

Release Management/Release Process Checklist Documentation (view source)

Revision as of 14:23, 12 September 2024

831 bytes added , 12 September 2024

Added beta1 steps covering "managed publishing" for Fenix and Focus

Dmeehan

362

edits

@@ Line 252: / Line 252: @@
 #* Taskcluster email: “firefox-android XXX.0b# build1/mozilla-beta is in the candidates directory"
 # Push Firefox Android (AC, Fenix, Focus) release in Ship-It via Push
-# Monitor for QA sign-off on desktop functional testing, before proceeding with Step 17.
+# Confirm notification sent when the Firefox Android (AC, Fenix, Focus) push finishes
+#* Taskcluster email: “Focus/Fenix XXXb#-build1 has been pushed to the closed testing track on Google Play"
+# Ship Firefox Android (AC, Fenix, Focus) from Ship-It via Ship
+# Turn on [https://support.google.com/googleplay/android-developer/answer/9859654?hl=en managed publishing] in the Play Console for Fenix.
+#* Fenix beta 1 only rolls out once QA sign-off.
+#* This allows you to submit an app for review but control when it is published.
+# Manually create a Fenix release on the Production track @ 25% rollout and submit for review
+#* 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.
+# 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
+# Monitor for QA sign-off on desktop functional testing before proceeding with Step 24.
 #* 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.
@@ Line 278: / Line 289: @@
 # Monitor for QA sign-off on desktop update testing
 #* QA will post a message to the [https://mozilla.slack.com/archives/CAC9YSH3P #qa-coordination] channel in Slack when they complete update testing.
-# Monitor for QA sign-off on Fenix/Focus build validation
+# Monitor for QA sign-off on Fenix/Focus build validation before proceeding with Step 34.
 #* Fenix build validation testing is tracked [https://mozilla-hub.atlassian.net/wiki/spaces/MTE/pages/21561505 here]
 #* Focus build validation testing is tracked [https://mozilla-hub.atlassian.net/wiki/spaces/MTE/pages/21561496 here]
 #* Please Note: Build Validation sign-off is usually provided the day after Fenix/Focus builds are produced.
 #* Focus and Fenix QA sign-off are sent via [https://mozilla.slack.com/archives/CAC9YSH3P #qa-coordination] Slack Channel
-#* Once QA has signed off, roll out Fenix to the production track at 25% in Google Play
+# Turn off managed publishing in the Play Console for Fenix
-#** See [https://play.google.com/console/u/0/developers/7083182635971239206/app/4972447553788559254/releases/overview Firefox for Android Beta]
+#* This allows the app to publish automatically once it passes review.
-#* Once QA has signed off, roll out Focus to the Closed testing - Foxfooding track at 25% in Google Play
+# Turn off managed publishing in the Play Console for Focus
-#** See [https://play.google.com/console/u/0/developers/7083182635971239206/app/4972137837611309386/releases/overview Firefox Focus (Beta for Testers)]
 # Monitor for QA sign-off on Firefox iOS build validation
 #* Build validation testing is tracked [https://mozilla-hub.atlassian.net/wiki/spaces/MTE/pages/21561470 here]
@@ Line 293: / Line 303: @@
 #* Build validation testing is tracked [https://mozilla-hub.atlassian.net/wiki/spaces/MTE/pages/21561465/Build+Validation+-+Focus+iOS here]
 # Verify the [https://product-details.mozilla.org/1.0/mobile_versions.json mobile_versions.json] is correct
-#* Verify the following beta_version is correct:
+#* Verify the beta_version is correct
-#* If this is incorrect, contact the RelEng on duty via the [https://matrix.to/#/#releaseduty:mozilla.org #release-duty] channel in Matrix.
+#* If incorrect, contact the RelEng on duty via the [https://matrix.to/#/#releaseduty:mozilla.org #release-duty] channel in Matrix.
 ==The following tasks need to be performed daily during the Beta cycle==