383
edits
Release Management/Release Process Checklist Documentation: Difference between revisions
Release Management/Release Process Checklist Documentation (view source)
Revision as of 14:30, 12 September 2024
, 12 September 2024Minor fixes
(Added beta1 steps covering "managed publishing" for Fenix and Focus) |
(Minor fixes) |
||
| Line 259: | Line 259: | ||
#* This allows you to submit an app for review but control when it is published. | #* 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 | # 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. | #* If an app is still pending review on a closed track then you cannot "promote" it to a production track. | ||
#* You can manually create the release by selecting the bundle that was pushed to the Play Console. | |||
#* Don't forget to edit the release name, for example change it to 101.0b1. | |||
#* See [https://support.google.com/googleplay/android-developer/answer/9859348?hl=en Prepare and roll out a release] for more information. | #* 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. | # 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 | # 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 | # Monitor for QA sign-off on desktop functional testing before proceeding with Step 23. | ||
#* 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 289: | Line 291: | ||
# 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 before proceeding with Step | # Monitor for QA sign-off on Fenix/Focus build validation before proceeding with Step 31. | ||
#* 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] | ||