Releng 4.3 #9898
Comments
|
#9898, #8520, #9890, #9703, #9892, #9893, #9692, #7208, #7212, #9670, #9767, #9698, #7157, #9731, #9852, #9606, #9855, #9295, #9843, #9793, #9798, #9677, #9827, #2818, #7314, #9810, #9797, #9495, #9682, #9784, #9750, #2768, #9770, #9461, #9631, #220, #9191, #9745, #9687, #9743, #9647, #9663, #9688, #9679, #3262, #9675, #9605, #9639, #9635, #9128, #9222, #9499, #9628, #7978, #8819, #6174, #8318, #9604, #9617, #9622, #9422, #768, #9308, #9433, #9466, #9233, #9306, #9336, #9353, #9423, #9426, #9533, #9553, #8125, #9365, #9598, #8697, #9599, #9549, #9574, #9564, #9394, #9109, #9561, #9472, #9552, #9330, #8412, #8903, #9530, #9189, #9439, #9525, #9132, #9524, #7720, #7059, #9498, #9496, #9500, #9469, #8764, #9252, #8017, #8568, #8485, #8968, #9280, #8651, #9435, #9352, #7356, #8944, #9443, #9402, #4987, #7734, #9442, #9414, #5208, #9395, #7661, #9290, #8288, #9333, #8972, #9207, #9364, #9351, #8809, #8759, #9346, #9347, #9359 |
|
4.3 at 100% |
Overview
Requirements
Release Checklist
There are two releases this covers: the current sprint that is going out to Beta, and the previous beta that is going to Production.
We will refer to the beta release going out as the current sprint release.
Start of sprint [Monday, 1st week of sprint]
Release Day [Monday, 3rd week] Beta & Production
vX.X.X(v2.3.0) with the previous Beta branch as the target.signing-productiontask to the release pageneed-infosomeone from release management.Create a branch off of master (DO NOT PUSH YET) for the current milestone of format
releases/v2.3(where 2.3 is the current milestone). After that, anything landing in master will be part of the next milestone.On the new Beta branch, pin the AC version to the stable version (example) with commit message "Issue #
<this releng issue>: Pin to stable AC<version>for release v2.3" (replacing 2.3 with the version)For each issue closed since the last release (run
kotlinc -script automation/releasetools/PrintMentionedIssuesAndPrs.ktsto get a list [see script for details] and paste it into the Releng issue):eng:qa:neededflags on each issue that still needs it.Go through the list of issues closed during this sprint in the Done column of the Sprint Kanban and make sure they all have the correct milestone.
Note: You will need code review to make changes to the release branch after this point, because it is a protected branch.
Create a GitHub pre-release build
vX.X.X-beta.1(v2.3.0-beta.1) with the release branch as the target. This will kick off a build of the branch. You can see it in the mouseover of the CI badge of the branch in the commits view. Builds are found undersigning-*task.If you need to trigger a new RC build, you will need to draft and publish a new (pre-release) release. Editing an existing release and creating a new tag will not trigger a new RC build.
Create a new PI (product integrity) request in Jira. You can clone this issue.
SUMO Verification [After Beta release]
During Beta Product Integrity (Beta Release until PI green signoff)
During Production Release Rollout [Tuesday, Wednesday following Monday Release Day]
Check Sentry for new crashes. File issues and triage.
Ask Relman in the bug if they see potential blockers on Google Play, and if not, request that they bump the release each day (25% Tu, 100% Wed)
Major releases often need to be synchronized with other marketing activities (e.g. blog postings).
Room for improvement
eng:qa:neededto issues Automate some manual parts of Releng Checklist #6199signing-productiontask look likepublic/build/arm64-v8a/geckoBeta/target.apk. This means that the dev must download, then rename them by hand. Could RM update these to generatepublic/build/arm64-v8a/geckoBeta/firefox-preview-v3.0.0-rc.1-arm64-v8a.apk, or similar?┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: