268
edits
Changes
no edit summary
#* The Firefox Android (Android-Components, Fenix, Focus) release branch is used for beta and rc builds. This step can be performed before the Beta 1 build has shipped to the beta channel, geckoview is built during the desktop promote phase.
# 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.
# 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 AS 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
#* Taskcluster email: “Focus/Fenix XXXb#-build1 is available at usual Taskcluster index"
# 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 1519.
#* 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.
#* Enable the Is Public checkbox and save
#** [[File:Screen Shot 2022-06-01 at 9.49.18 AM.png|thumb|center]]
#* Share a link to the Beta release notes URL and the release notes draft document in [https://mozilla.slack.com/archives/C9L102H6X #release-notes] Slack channel#** Also mention, if anyone has any feature worth a release note but not yet listed, they can nominate it via the relnote-firefox ? flag in BugzillaSee [https://mozilla.slack.com/archives/C9L102H6X/p1686065646980339 example]
# 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
#* 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, with wording such as:#** [mobile] Focus Beta xxx.0.0-beta.1 - Manual testing sign-off [GREEN]#** [Mobile] Firefox Beta xxx.0.0-beta.1 - Manual testing sign-off[GREEN]
#* Once QA has signed off, roll out Fenix to the production track at 25% in Google Play
#** See [https://play.google.com/console/u/0/developers/7083182635971239206/app/4972447553788559254/releases/overview Firefox for Android Beta]
#* Once QA has signed off, roll out Focus to the Closed testing - Foxfooding track at 25% in Google Play
#** 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
#* Once QA has signed off, add the External Beta Testers group to the TestFlight Build
# Verify the [https://product-details.mozilla.org/1.0/mobile_versions.json mobile_versions.json] is correct
#* Verify the following 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.
==The following tasks need to be performed daily during the Beta cycle==
