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
  • ⚠️ Remove deprecated flag for old infra machine naming #11679
    • Blocked by 🌱 Add NamingStrategy to MachineDeployment #11172

Week 3:

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

Week 7:

• [Release Lead] Cut the v1.9.5 & v1.8.10 releases Tuesday, February 18
  • CAPI v1.9.5
  • CAPI v1.8.10
• [Release Lead] [Track] Bump dependencies
  • 🌱 Bump controller-gen to v0.17.2 #11866
  • 🌱 Bump kustomize to v5.6.0 #11867

Week 11:

• [Release Lead] Create release-1.10 branch Tuesday, March 18
• [CI Manager] Setup jobs and dashboards for the release-1.10 release branch Tuesday, March 18
• [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
• [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
  • 🌱 Bump go to v1.23.5 #11714
  • [release-1.8] 🌱 Bump go to v1.22.11 #11738
  • [release-1.9] 🌱 Bump go to v1.22.11 #11739
  • 🌱 Bump go to v1.23.6 #11803
  • [release-1.9] 🌱 Bump go to v1.22.12 #11804
  • [release-1.8] 🌱 Bump go to v1.22.12 #11805
• [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

[mboersma]

@fabriziopandini @sbueringer this is updated with the changes to release-v1.10.md. Could someone take a quick look and triage this?

[sbueringer]

@mboersma

I moved "Setup jobs and dashboards for the release-1.10 release branch" to week 11.

Additionally I added a task in the same week to create the release branch. Usually our release GitHub action creates the branch automatically when the first RC tag is created. But in this case we have to create the branch earlier manually.

I hope we don't run into any additional problems because release tooling might assume that beta releases are cut against main instead on top of a release branch.

(cc @chrischdi I don't remember the exact problems we hit in that area in CAPV, but I think the problems in CAPV might be different because we run the release-notes tool not manually there)

But anyway, we're around. So we can help if we run into problems then

[mboersma]

Thanks @sbueringer! I'll investigate whether the tools may have a problem cutting a beta from the release branch.