Argo CD Release v2.14

[rumstead]

Target RC1 date: Monday, Dec. 16, 2024
Target GA date: ___. __, ____

• 1wk before feature freeze post in #argo-contributors that PRs must be merged by DD-MM-YYYY to be included in the release - ask approvers to drop items from milestone they can’t merge
• At least two days before RC1 date, draft RC blog post and submit it for review (or delegate this task)
• Cut RC1 (or delegate this task to an Approver and coordinate timing)
• Create new release branch
  • Add the release branch to ReadTheDocs
  • Confirm that tweet and blog post are ready
  • Trigger the release
  • After the release is finished, publish tweet and blog post
  • Post in #argo-cd and #argo-announcements with lots of emojis announcing the release and requesting help testing
• Monitor support channels for issues, cherry-picking bugfixes and docs fixes as appropriate (or delegate this task to an Approver and coordinate timing)
• At release date, evaluate if any bugs justify delaying the release. If not, cut the release (or delegate this task to an Approver and coordinate timing)
• If unreleased changes are on the release branch for {current minor version minus 3}, cut a final patch release for that series (or delegate this task to an Approver and coordinate timing)
• After the release, post in #argo-cd that the {current minor version minus 3} has reached EOL (example: https://cloud-native.slack.com/archives/C01TSERG0KZ/p1667336234059729)
• (For the next release champion) Review the items scheduled for the next release. If any item does not have an assignee who can commit to finish the feature, move it to the next release.
• (For the next release champion) Schedule a time mid-way through the release cycle to review items again.