Release management checklist - v4.5

[severinrudie]

Sprint Release Owner: @dnarcese

Think something can be automated? Add it to this doc.

Tuesday # 1

• Upgrade a-c

Wednesday # 1

• Verify all strings have been landed; exports now happen automatically
• 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)
• Release LAT (instructions)
  • Email team announcing release (template/instructions)

Wednesday # 2 (soft code freeze = noon PT)

• 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)
• Release LAT (instructions)
  • Email team announcing release (instructions)

Thursday # 2

• [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 to bump version (X.X) and update changelog against master
  • Update the CHANGELOG: glance over the changelog to see if any major
    features are missing and add the new release header
  • Merge to master
• Cut release branch releases/vX.X from releases/vX.X-LAT2
  • Create PR to bump version ('X.X') and update changelog against branch releases/vX.X
  • Merge to releases/vX.X
• Create GitHub release build vX.X(instructions)
• Submit app with staged rollout at 1% (instructions)
  • Email team announcing release (instructions)

Tuesday # 3

• [QA] sign-off
• Bump rollout to 20% Waiting for change in desktop: consult with Ashley
  • Email team announcing release (instructions)

Wednesday # 3

• [QA] sign-off
• Bump rollout to 100% Waiting for change in desktop: consult with Ashley
  • Email team announcing release (instructions)