383
edits
Release Management/Release Process Checklist Documentation: Difference between revisions
Jump to navigation
Jump to search
Release Management/Release Process Checklist Documentation (view source)
Revision as of 14:23, 12 September 2024
, 12 September 2024Added beta1 steps covering "managed publishing" for Fenix and Focus
(minor wording tweaks) |
(Added beta1 steps covering "managed publishing" for Fenix and Focus) |
||
| Line 252: | Line 252: | ||
#* Taskcluster email: “firefox-android XXX.0b# build1/mozilla-beta is in the candidates directory" | #* 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 | # Push Firefox Android (AC, Fenix, Focus) release in Ship-It via Push | ||
# Monitor for QA sign-off on desktop functional testing | # 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. | #* 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. | #* 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 | # 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. | #* 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] | #* 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] | #* 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. | #* 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 | #* Focus and Fenix QA sign-off are sent via [https://mozilla.slack.com/archives/CAC9YSH3P #qa-coordination] Slack Channel | ||
# | # Turn off managed publishing in the Play Console for Fenix | ||
#* | #* This allows the app to publish automatically once it passes review. | ||
# | # Turn off managed publishing in the Play Console for Focus | ||
# Monitor for QA sign-off on Firefox iOS build validation | # 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] | #* 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] | #* 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 [https://product-details.mozilla.org/1.0/mobile_versions.json mobile_versions.json] is correct | ||
#* Verify the | #* Verify the beta_version is correct | ||
#* If | #* 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== | ==The following tasks need to be performed daily during the Beta cycle== | ||