Release Management/Release Process Checklist Documentation: Difference between revisions

Jump to navigation Jump to search
Adding new metrics page
No edit summary
(Adding new metrics page)
Line 387: Line 387:
#** ''moz-phab patch <patch id> --no-bookmark --apply-to here''
#** ''moz-phab patch <patch id> --no-bookmark --apply-to here''
#* Edit the commit message to add the approval.
#* Edit the commit message to add the approval.
# Update the Beta Quality Metrics in the Mana release tracking page, a child page of Firefox Release Tracking is created per release.
# Use the Mana [https://mozilla-hub.atlassian.net/wiki/spaces/FIREFOX/pages/277284167/Beta+Quality+Metrics Beta Quality Metrics Page] to review the Beta Quality Metrics.
#* Add a new column In the Beta Quality Metrics table using the current beta version as the title.
#* The data is embedded from this [https://docs.google.com/spreadsheets/d/1Ev8HSxyAQFB5eLX98r6hmDR7FFNViJD4JWnqxiEtx48/edit#gid=2061648925 wiki page].
#* Add data from each of corresponding the metrics URLs (Bugzilla/telemetry) in the Metric Name column.
#* The data is currently added manually.
#** Ensure to add the Firefox metric, not the target metric.
#** The data is stored automatically every day in bugzilla using [https://bugzilla.mozilla.org/chart.cgi?category=-All-&datefrom=2023-08-16&dateto=2023-08-30&label0=1%20function-open-blockers&label1=%202%20function-unfixed-new-regressions&label2=3%20function-open-carryover-regressions%20&label3=4%20function-severe-carryover-regression&label4=5%20stability-new-top-crashers&label5=6%20stability-tracked-crashers&label6=7%20Perf-bugs-affecting-beta&label7=8%20sec-all-high-crit-affecting-beta%20&line0=7748&line1=7779&line2=7780&line3=7765&line4=7766&line5=7747&line6=7754&line7=7756&name=7756&subcategory=-All-&action=assemble New Charts]
#** While gathering the telemetry data metrics, take a look at the metric over time to ensure the value is stable.  
#** To extract the data, run the report by adding the next needed dates and then exporting to csv. (The queries are numbered to make this step easier)
#** Please Note: Ensure to update this prior to the Tuesday channel meeting.
#** This is then manually pasted into the 'Data from Queries' tab.
#** Please Note: the goal is to automate this.
#* Take a look at the metric/charts over time to ensure the value is stable.  
#** Please Note: Ensure the data is updated prior to the Tuesday channel meeting.
# Update the Weekly Digest document, as requested on the [https://mozilla.slack.com/archives/C01TTHGPSKB #fx-weekly-digest] Slack channel.
# Update the Weekly Digest document, as requested on the [https://mozilla.slack.com/archives/C01TTHGPSKB #fx-weekly-digest] Slack channel.
#* Update the Release Milestones (Details) section to add Status (On Track, Delayed), Ship Date, information on the current beta release for both Desktop/DeveEdition and Fenix/Focus, information on where we are in the Beta cycle for example when coming up to end of early beta.
#* Update the Release Milestones (Details) section to add Status (On Track, Delayed), Ship Date, information on the current beta release for both Desktop/DeveEdition and Fenix/Focus, information on where we are in the Beta cycle for example when coming up to end of early beta.
255

edits

Navigation menu