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 19:50, 18 March 2024

547 bytes removed ,  18 March 2024
no edit summary
No edit summary
No edit summary
Line 191: Line 191:
# Perform the release management steps in the [https://github.com/mozilla-mobile/firefox-ios/wiki/Release-Checklist#soft-freeze-tasks Firefox iOS Soft Freeze Checklist]
# Perform the release management steps in the [https://github.com/mozilla-mobile/firefox-ios/wiki/Release-Checklist#soft-freeze-tasks Firefox iOS Soft Freeze Checklist]
#* The Firefox iOS release branch is used for beta and rc builds.
#* The Firefox iOS release branch is used for beta and rc builds.
# Branch focus-ios from main to releases_vxxx
#* Create a branch name with the format releases_v[beta_version] off of the [https://github.com/mozilla-mobile/focus-ios main branch] (for example, releases_v109) through the GitHub UI. [beta_version] should follow the Firefox Beta release number.
# Bump the version by running [https://github.com/mozilla-mobile/focus-ios/blob/main/tools/set-version.sh set-version.sh script] in the releases_v[beta_version] branch of focus-ios
# Pin the Application-Services version in the focus-ios release branch
#* See [https://github.com/mozilla-mobile/focus-ios/pull/3804 Example PR]
# Review any pending uplifts that may be required before proceeding with a beta 1 build
# Review any pending uplifts that may be required before proceeding with a beta 1 build
#* This should not be a common occurrence, however, an example would be a crash fix that may have landed in central post-merge.
#* This should not be a common occurrence, however, an example would be a crash fix that may have landed in central post-merge.
Line 237: Line 232:
#* Taskcluster email: “Focus/Fenix XXXb#-build1 is available at usual Taskcluster index"
#* Taskcluster email: “Focus/Fenix XXXb#-build1 is available at usual Taskcluster index"
# 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, before proceeding with Step 19.  
# Monitor for QA sign-off on desktop functional testing, before proceeding with Step 17.  
#* 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 247: Line 242:
#* View the [https://balrog.services.mozilla.com/rules?product=Firefox&channel=aurora Balrog Rules for Aurora (DevEdition)]
#* View the [https://balrog.services.mozilla.com/rules?product=Firefox&channel=aurora Balrog Rules for Aurora (DevEdition)]
#** Verify that the Background rate for Devedition-xxx.0b1-build1 is 100
#** Verify that the Background rate for Devedition-xxx.0b1-build1 is 100
# Email release-signoff with a confirmation that updates are live.
#* [https://groups.google.com/a/mozilla.org/g/release-signoff/c/7dOVz6wgP9w Email Example]
# Activate automated betas in [https://shipit.mozilla-releng.net/ Ship-It]
# Activate automated betas in [https://shipit.mozilla-releng.net/ Ship-It]
## At the bottom of the page, click the red x beside Firefox Desktop: Beta
## At the bottom of the page, click the red x beside Firefox Desktop: Beta
Line 276: Line 269:
# 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]
#* Once QA has signed off, add the External Beta Testers group to the TestFlight Build
#* Once QA has signed off, add the External Beta Testers group to the Firefox iOS TestFlight Build
# Monitor for QA sign-off on Focus iOS build validation
#* 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 following beta_version is correct:
#* Verify the following beta_version is correct:
Line 340: Line 335:
# Promote Fenix to the Production track @ 50% b2 and @ 99% b3+
# Promote Fenix to the Production track @ 50% b2 and @ 99% b3+
#* See [https://play.google.com/console/u/0/developers/7083182635971239206/app/4972447553788559254/releases/overview Firefox for Android Beta]
#* See [https://play.google.com/console/u/0/developers/7083182635971239206/app/4972447553788559254/releases/overview Firefox for Android Beta]
# Promote Focus to the closed testing track (Foxfooding) @ 50% b2 and @ 99% b3+
# Promote Android Focus to the closed testing track (Foxfooding) @ 50% b2 and @ 99% b3+
#* See [https://play.google.com/console/u/0/developers/7083182635971239206/app/4972137837611309386/releases/overviewFirefox Focus (Beta for Testers)]
#* See [https://play.google.com/console/u/0/developers/7083182635971239206/app/4972137837611309386/releases/overviewFirefox Focus (Beta for Testers)]
# Confirm notification sent when the Desktop and DevEditon CDN push finishes.
# Confirm notification sent when the Desktop and DevEditon CDN push finishes.
Line 368: Line 363:
#* Firefox iOS QA sign-off are sent via [https://mozilla.slack.com/archives/CAC9YSH3P #qa-coordination] Slack Channel.
#* Firefox iOS QA sign-off are sent via [https://mozilla.slack.com/archives/CAC9YSH3P #qa-coordination] Slack Channel.
#* Please Note: Build Validation sign-off is usually provided the day after Firefox iOS builds are produced. If the sign-off is yellow/red, then follow-up on the [https://mozilla.slack.com/archives/C03PKCHHSSD #firefox-ios-releases] Slack channel. Ensure a plan is in place or a decision is made to block/proceed with the release.
#* Please Note: Build Validation sign-off is usually provided the day after Firefox iOS builds are produced. If the sign-off is yellow/red, then follow-up on the [https://mozilla.slack.com/archives/C03PKCHHSSD #firefox-ios-releases] Slack channel. Ensure a plan is in place or a decision is made to block/proceed with the release.
#* Once QA has signed off add the External Testers group.
#* Once QA has signed off add the External Testers group to Firefox iOS.
#** Reply to the QA sign-off Slack message.
#** Reply to the QA sign-off Slack message.


Dmeehan
273

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1250273"

Navigation menu