268
edits
Changes
no edit summary
#* 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.
#* Build validation testing is tracked [https://mozilla-hub.atlassian.net/wiki/spaces/FDPDT/pages/10617980/Firefox+regression+testing here]
# Once QA has signed off, push Desktop and DevEdition to Beta in [https://shipit.mozilla-releng.net/ Ship-It] via Ship.
# Verify that the Balrog rule changes are live and correctly set.
#* Ensure that the tickets are progressing, and follow up as required.
# Monitor '''Newly-filed regression bugs'''
#* New regressions bugs can be found [https://wikibugdash.mozillamoz.orgtools/Platform#Bug_Lists tab.reo here]
#* Review with the REO - ensure that new tickets are prioritized and ensure that carry-over tickets are still on the team’s radar
# Monitor '''stability rates and reported crash spikes'''
#* Leverage the automated emails, monitor top crashes in [https://crash-stats.mozilla.org/ crash-stats], and monitor [https://metricsmozilla.mozillacloud.looker.com/public/sguhadashboards/mc2/missioncontrol_v2.html Mission Control918?Channel=beta&OS+Name=&Ten+Percent+Sample=Yes Stability & Release Monitoring]
#* Ensure that there are tickets tracking issues with stability rates and crash spikes
# Monitor the '''Release Notes requests''' for Beta Tickets.
# Create a tab in the release tracking sheet “xxx.0bx”
#* Use the relevant beta macro#* Please note: After all the Desktop beta has shippedsteps are complete, the tab can be hidden in order to minimize clutter.
# Review tracking-firefoxXX+ bugs and approval requests.
#* This step is performed as part of the daily activities, tracked in the checklist for confirmation.
#* View the [https://balrog.services.mozilla.com/rules?product=Firefox&channel=aurora Balrog Rules for Aurora (DevEdition)]
#** Verify that the Background rate for Devedition-xx.0b1-buildx is 100.
# Email release-signoff with a confirmation that updates are live.#* Beta 2 Subject: “[desktop] Ensure the Firefox Desktop & DevEdition xxx.0b2 are live”iOS build is available in Testflight#* Beta 2 Body: “Firefox Desktop & DevEdition xxx.0b2 are live on If the build is not pushed then check the build status in the Beta and #* Aurora channels at 50% and 100% rollout, respectively.”#* Beta 3+ Subject: “[desktop] Firefox Desktop & DevEdition xxx.0bx are live @ 100% rollout [EOM]”#* Beta 3+ Bodyhttps: N/A#* Please Note: For the final beta release email, mention it was the last beta/app.#** Subject: [desktop] Firefox Desktop & DevEdition xxxbitrise.0bx are live @ 100% rollout, this was the last beta [EOMio/app/6c06d3a40422d10f?workflow=workflow-SPM_Deploy_Prod_Beta BitRise pipeline]
# Monitor for QA sign-off on Desktop and DevEdition build validation for both update/functional testing.
#* QA will post a message to the [https://mozilla.slack.com/archives/CAC9YSH3P #qa-coordination] channel in Slack when they complete update testing and another message when they complete functional testing.
#* Build validation testing is tracked [https://manamozilla-hub.mozillaatlassian.orgnet/wiki/spaces/FDPDT/pages/viewpage.action?pageId=162277457 10617980 here]
# Monitor for QA sign-off on Fenix/Focus build validation before proceeding with bumping the Fenix/Focus rollout.
#* 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.x - Manual testing sign-off [GREEN]#** [Mobile] Firefox Beta xxx.0.0-beta.x - Manual testing sign-off[GREEN]#* Please Note: Build Validation sign-off is usually provided the day after Fenix/Focus builds are produced. If the sign-off is yellow/red, then follow-up on the relevant [https://mozilla.slack.com/archives/C016PEDKY90 #mobile-android-team ] Slack channel. Ensure a plan is in place or a decision is made to block/proceed with the release.
#* For b3+ once QA has signed off, roll out Fenix to the production track in Google Play to 100%.
#** Reply to the QA sign-off slack Slack message and include the rollout percentage.
#* For b3+, once QA has signed off, roll out Focus to the Closed testing - Foxfooding track in Google Play to 100%.
#** Reply to the QA sign-off slack Slack message and include the rollout percentage.# Monitor for QA sign-off on Firefox iOS build validation before proceeding with adding the External Testers group in TestFlight.#* 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.#* Once QA has signed off add the External Testers group.#** Reply to the QA sign-off Slack message.
==As available, the following items should be monitored during the Beta cycle==
==The following needs to be performed at the end of the Beta Cycle==
# Disable automated beta builds in Ship-it.# Disable the firefox-ios firefox-ios SPM_Deploy_Prod_Beta BitRise scheduled workflow.#* Expand the Scheduled section in the [https://app.bitrise.io/app/6c06d3a40422d10f firefox-ios on BitRise]#* Disable the SPM_Deploy_Prod_Beta that runs "Every Tue, Thu, Sun @ 20:00"
# Please Note: Monitor beta/release uplift requests between the final beta build and the beta to release merge. It is possible that a late uplift request may come in for a regression/stability fix, evaluate if this is a blocker for the RC and if it should be uplifted to beta before the beta to release merge and RC build.
