_Think something can be automated? Add it to this doc._
Tuesday # 1
[ ] Upgrade a-c
Wednesday # 1
[ ] 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)
[ ] [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
Friday # 2 (hard code freeze)
[ ] [Product, QA, eng] sign-off for release
Monday # 3
[ ] 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)
[ ] 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)
Sprint Release Owner: [name here]
_Think something can be automated? Add it to this doc._
Tuesday # 1
Wednesday # 1
strings-readyissues in Sprint have strings landed (exports now happen automatically). If not, check with L10N/PM if the issue needs to be removed from Sprint.X.X-LAT1)releases/vX.X-LAT1(this must include a-c upgrade)vX.X-LAT1(instructions)Wednesday # 2 (soft code freeze = noon PT)
X.X-LAT2)releases/vX.X-LAT2vX.X-LAT2(instructions)Thursday # 2
Friday # 2 (hard code freeze)
Monday # 3
X.X) and updating changelogreleases/vX.XvX.X(instructions)Tuesday # 3
Wednesday # 3