6.2 KiB
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.
| Monday | Tuesday | Wednesday | Thursday | Friday |
|---|---|---|---|---|
| String Freeze | ||||
| Soft Code Freeze | QA | Hard Code Freeze/Localization Due/Planning | ||
| Release to Play Store |
Requirements
- Jira account
- Bugzilla account
- Google Play access (for reviewing crashes)
Release Checklist
We will refer to the release that is going out as the current release.
Start of sprint [Monday, 1st week of sprint]
- Create milestone for upcoming release. (e.g. if you are doing releng for v2.2, create v2.3 milestone)
- If the upcoming release is a major (x.0) release, create an issue in the upcoming milestone: "What's New Entry for [upcoming release]" to track work for the SUMO page and Google Play release notes, e.g., if the current release is 2.3 but the upcoming one will be 3.0, make a "What's New" issue for 3.0. Product will use this to remember to check in with SUMO.
- Create an issue in the upcoming milestone: "Releng for v[release]". Find an engineer who will handle the next releng task and assign them.
String freeze [Tuesday, 1st week of sprint]
- Make sure all issues with label needs:strings and eng:ready have strings provided in comment 0. If there are no strings, ping the Content team in #fenix-team channel to provide them. (Content is @jpfaller, or @mheubusch)
- Open a PR with all new strings in the
needs:stringslabel that have not yet been merged to master - For each string included in the PR, update its issue's
strings:neededlabels from the PR toapproved:strings
String freeze follow-up [Wednesday, 1st week of sprint]
- For any strings still labeled
needs:strings- If strings have been provided by content team, open a PR with the newly provided strings. Update their
strings:neededlabels toapproved:strings - Otherwise, escalate to Product because this may miss the release.
- If strings have been provided by content team, open a PR with the newly provided strings. Update their
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:neededflags 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.
- Push the branch.
-
On GitHub, draft a GitHub Release with with a tag of the format
v2.3.0-rc.1with 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.- 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.
-
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]
- If the current release is a major (x.0) release, review the SUMO article contents of the whats new / other sumo pages and make sure they are accurate with what is in this release. If not, escalate to Product Owner.
During Product Integrity (Soft code freeze until PI green signoff)
- Check Google Play for new crashes. File issues and triage.
- If bugs are considered release blocker then find someone to fix them on master and the milestone branch (cherry-pick / uplift)
- If needed tag a new RC version (e.g. v1.0-RC2) and follow the submission checklist again.
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-infosomeone from release management.- Release management promotes the build from beta to the release channel. For minor releases this can happen at any time during the day. Major releases often need to be synchronized with other marketing activities (e.g. blog postings). Releases are rolled out to 99% of the population (otherwise the rollout can't be stopped).
After the release
- Check whether there are new crashes that need to be filed.
- Follow up with Product about releasing to 100%.
- In the Bugzilla bug, ask release management to set the rollout to 100%.