-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Releng for v3.0 #6302
Comments
Note re: #6354 |
I filtered out the #s that point to PRs. Those that point to issues are named:
|
Boiled the above down to.
🤦♂ so much wasted work |
Hey @bifleming @liuche, the process of going through these issues took a few hours, and was very manual. I've scripted some of it, so hopefully it'll be a bit quicker next time, but it still feels like a lot given the eventual output. I'm not sure what we should be doing instead, but I think finding a better solution to this should be on our radar. On FFTV one of our 'definition of done' reqs was adding a line to a changelog that we maintained in source control. That would definitely speed this portion up, but wouldn't give us an opportunity to clean up missed milestones / qa status on issues. Food for thought. |
Per @liuche: with the beta cycle, on the 3rd Tuesday of the cycle (today) we would normally release the previous version. Since this is the first beta cycle, nothing will happen today. 3.0 will be promoted to release on the next cycle. The release docs will soon be updated with more details regarding betas. |
Will also need to uplift strings, like #6530 |
@baron-severin since we're planning on launching on Dec 2, I think the last string uplifts can happen this week, so all that needs to happen is tag the release and ask Relman to release. |
@boek and I attempted to uplift strings, but there were a very large number of merge conflicts and the vast majority of strings were for features that do not exist in 3.0. We timeboxed this to about an hour (trying several different approaches) and moved on to other work. I think 3.0 has diverged a lot more from master than is normal, given the unusual nature of this release. |
EDIT
For 3.0, due to an ongoing experiment we're collecting data for, we're not going to release until 12/3.
Overview
Soft code freeze for a release is the second Wednesday of the sprint, and most of releng happens between Wednesday and Friday, String freeze is the first Tuesday of the sprint.
Requirements
Release Checklist
We will refer to the release that is going out as the current release.
Start of sprint [Monday, 1st week of sprint]
String freeze [Tuesday, 1st week of sprint]
needs:strings
label that have not yet been merged to masterstrings:needed
labels from the PR toapproved:strings
String freeze follow-up [Wednesday, 1st week of sprint]
needs:strings
strings:needed
labels toapproved:strings
Soft code freeze [Wednesday, 2nd week of sprint]
Merge any remaining automated L10N string PRs.
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 Release 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)Go through the list of issues closed during this sprint and make sure they all have the correct milestone.
Add
eng:qa:needed
flags on each issue that still needs it.Note: You will need code review to make changes to the release branch after this point, because it is a protected branch.
On GitHub, draft a GitHub Release with with a tag of the format
v2.3.0-rc.1
with the release branch as the target. Check the pre-release checkbox. 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.Upload the APK from the Taskcluster signing task to the releases page.
Create a new PI (product integrity) request in Jira. You can clone this issue.
SUMO Verification [Thursday, 2nd week of sprint]
During Product Integrity (Soft code freeze until PI green signoff)
Release to Google Play Store [Tuesday, 3rd week]
Tag the latest released RC version additionally with the tag of the release (v1.0-RC2 -> v1.0) (This can be done as soon as there are no more release blockers, does not need to be on Release Day.)
Upload signed APKs to the release page
Create a release request in Bugzilla. You can clone this issue and
need-info
someone from release management.After the release
Room for improvement
eng:qa:needed
to issues Automate some manual parts of Releng Checklist #6199┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: