Changes

# 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.

# 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.

#* Taskcluster email: “Focus/Fenix XXXb#-build1 is available at usual Taskcluster index"

# Push Firefox Android (AC, Fenix, Focus) release in Ship-It via Push

#* 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.

#* 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

# 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

# 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]

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

#* Verify the following beta_version is correct:

# 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/4972137837611309386/releases/overviewFirefox Focus (Beta for Testers)]

# Confirm notification sent when the Desktop and DevEditon CDN push finishes.

#* 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.

#** Reply to the QA sign-off Slack message.