Tasks for v1.10 release cycle

[mboersma]

Please see the corresponding sections of the role-handbooks for documentation of individual tasks. See CAPI v1.10 release improvement tasks for additional tracking info.

Tasks

Week 1:

• [Release Lead] Finalize release schedule and team Friday, January 10
  • 📖 Update Cluster API release-1.10 release team members #11648
• [Release Lead] Add/remove release team members Friday, January 10
  • 📖 Update Cluster API release-1.10 release team members #11648
  • CAPI: Update with v1.10 release team members kubernetes/org#5335
  • CAPI: Update v1.10 release team members kubernetes/community#8241
• [Release Lead] Prepare main branch for development of the new release
  • 🌱 Prepare main branch for v1.10 development #11647
• [Communications Manager] Add docs to collect release notes for users and migration notes for provider implementers
• [Communications Manager] Update supported versions

Week 1 to 4:

• [Release Lead] [Track] Remove previously deprecated code

Week 3:

• [Release Lead] Cut the v1.9.4 & v1.8.9 releases Tuesday, January 21

Week 7:

• [Release Lead] Cut the v1.9.5 & v1.8.10 releases Tuesday, February 18

Week 10 to 11:

• [Release Lead] [Track] Bump dependencies

Week 11:

• [Release Lead] Cut the v1.10.0-beta.0 release Tuesday, March 18
• [Release Lead] Create a new GitHub milestone for the next release
• [Communications Manager] Communicate beta to providers Tuesday, March 18
• [Release Lead] Cut the v1.9.6 & v1.8.11 releases Tuesday, March 18

Week 12:

• [Release Lead] Cut the v1.10.0-beta.1 release Tuesday, March 25
• [Release Lead] Set a tentative release date for the next minor release
• [Release Lead] Assemble next release team
• [Release Lead] Select release lead for the next release cycle

Week 13:

• Kubecon idle week April 1-4

Week 14:

• [Release Lead] Cut the v1.10.0-rc.0 release Tuesday, April 8
• [Release Lead] Update milestone applier and GitHub Actions Tuesday, April 8
• [CI Manager] Setup jobs and dashboards for the release-1.10 release branch Tuesday, April 8
• [Communications Manager] Ensure the book for the new release is available Tuesday, April 8

Week 15:

• [Release Lead] Cut the v1.10.0-rc.1 release Tuesday, April 15

Week 16:

• [Release Lead] Cut the v1.10.0 release Tuesday, April 22
• [Release Lead] Cut the v1.9.7 & v1.8.12 releases Tuesday, April 22
• [Release Lead] Organize release retrospective
• [Communications Manager] Change production branch in Netlify to the new release branch
• [Communications Manager] Update clusterctl links in the quickstart

Week 17:

• [Release Lead] Cut the v1.10.1 release Tuesday, April 29

Continuously:

• [Release lead] Maintain the GitHub release milestone
• [Release lead] Bump the Go version
• [Communications Manager] Communicate key dates to the community
• [Communications Manager] Improve release process documentation
• [Communications Manager] Maintain and improve user facing documentation about releases, release policy and release calendar
• [CI Manager] Monitor CI signal
• [CI Manager] Reduce the amount of flaky tests

If and when necessary:

• [Release Lead] [Track] Bump the Cluster API apiVersion
• [Release Lead] [Track] Bump the Kubernetes version
• [Release Lead] Track Release and Improvement tasks

/priority critical-urgent
/kind feature

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[mboersma]

/assign