name | about | title |
---|---|---|
✅ Release management checklist |
Keep track of the release activities |
Release management checklist - vX.X |
Think something can be automated? Add it to this doc.
- Upgrade a-c
- Verify all
strings-ready
issues in Sprint have strings landed (exports now happen automatically). If not, check with L10N/PM if the issue needs to be removed from Sprint. - Create PR for bumping version (
X.X-LAT1
)- Merge to master
- Cut LAT branch
releases/vX.X-LAT1
(this must include a-c upgrade) - Create GitHub pre-release build
vX.X-LAT1
(instructions) - Wait for automation to email the team mailing list, signalling that the build is done
- Release LAT (instructions)
- Email team announcing release (template/instructions)
- Create PR for bumping version (
X.X-LAT2
)- Merge to master
- Cut LAT branch
releases/vX.X-LAT2
- Create GitHub pre-release build
vX.X-LAT2
(instructions) - Wait for automation to email the team mailing list, signalling that the build is done
- Release LAT (instructions)
- Email team announcing release (instructions)
- [QA] run screenshot test and upload (instructions)
- Upgrade a-c on master
- File new Release Management checklist with next version and add to top of Backlog
- [Product, QA, eng] sign-off for release
- Create PR for bumping version (
X.X
) and updating changelog- Update the CHANGELOG: glance over the changelog to see if any major features are missing and add the new release header (don't forget to add the diff links at the bottom)
- Merge to master
- Cut release branch
releases/vX.X
- Create GitHub release build
vX.X
(instructions) - Wait for automation to email the team mailing list, signalling that the build is done and uploaded to a pending "upcoming release" in the Amazon console
- Submit app with staged rollout at 1% (instructions)
- Email team announcing release (instructions)
- [QA] sign-off
- Bump rollout to 20%
- Email team announcing release (instructions)
- [QA] sign-off
- Bump rollout to 100%
- Email team announcing release (instructions)