Release v1.126.X

[jaredlockhart]

Welcome Release Captain! ⛵️

• Assign this issue to yourself
• Create 1.127.0 Milestone (due date two weeks from [when you read this, not two weeks from last milestone])
• Move all open tickets in 1.126.0 to 1.127.0 [if any]
• Close 1.126.0 Milestone
• Approve and merge all open dependabot[/renovate] PRs
• Pull master
• Ensure all linting and tests pass
  • With docker: make check
  • Without docker:
    • set +H
    • shopt -s extglob
    • therapist run --disable-git ./!(node_modules|assets|docs)
    • pytest
• git tag v1.126.0; git push --tags
• @here deploying normandy v1.126.0 to stage https://github.com/mozilla/normandy/milestone/7?closed=1 in #normandy
• Quickly verify that stage loads with v1.126.0
  • Wait for delivery notifications in #delivery-notifications to indicate that stage is being built and deployed
  • Verify that https://stage.normandy.nonprod.cloudops.mozgcp.net/__version__ shows the new version number
  • Fetch https://stage.normandy.nonprod.cloudops.mozgcp.net/api/v3/recipe/ or some other endpoint and verify that you get a 200
• File Bugzilla Release Bug with content copied from ./bin/generate_deploy_bug.py v1.125.4 v1.126.0
• Add release bug to comments in this issue
• Add QA :cmuresan as QA contact on the bugzilla ticket
• Await QA green sign off
• Point releases as necessary:
  • git checkout v1.126.X (last tag)
  • git cherry-pick <commit hash> commits to be cherry picked into point release
  • Run linting/tests (see above)
  • git tag v1.126.(X+1)
  • git push --tags
  • Update bugzilla ticket with ./bin/generate_deploy_bug.py v1.126.X v1.126.(X+1)
• @bpitts please deploy normandy v1.126.X to prod <bugzilla link> in #normandy where X is last point release and is the link to the bugzilla ticket created above
• Verify that prod loads with v1.126.0
• Create release issue for Release v1.127.0

[glasserc]

https://bugzilla.mozilla.org/show_bug.cgi?id=1587547

[glasserc]

Blocked on #2021.

[glasserc]

v1.126.1 is now on prod.