268
edits
Changes
no edit summary
#* Sync with the RelEng on duty. The RelEng on duty is listed in the Matrix channel description
# Create a Desktop Beta Checklist and Mobile Beta Checklist for beta 1
#* Copy Use the Desktop Beta Checklist template and the Mobile Beta Checklist#* Please Note: Depending on the Beta, some steps are irrelevant. Set the Status to N/A for these steps.b1 macro
# Wait for RelEng to complete the central to beta merge.
#* Use the [https://matrix.to/#/#releaseduty:mozilla.org #releaseduty] channel on Matrix to synchronize if needed.
==The following tasks need to be performed on Merge Day at the start of the Beta cycle after the merge to beta is finished==
# Perform the release management steps in the [https://mozac.org/contributing/release-checklist AC Release checklist]
#* 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]
# 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.
#* Taskcluser email: “firefox xxx.0b1 build1/mozilla-beta has been pushed to cdntest”
#* Taskcluser email: “devedition xxx.0b1 build1/mozilla-beta has been pushed to cdntest”
# Confirm GV bump PR is merged to the firefox-android releases_vXXX branch
#* The GeckoView build is created during the promote phase of the desktop build
