Tasks for v1.5 release cycle

[joekr]

Please see the corresponding section in release-tasks.md for documentation of individual tasks.

Tasks

Notes:

• Weeks are only specified to give some orientation.
• The following is based on the v1.4 release cycle. Modify according to the tracked release cycle.

Week -3 to 1:

• [Release Lead] Set a tentative release date for the minor release
• [Release Lead] Assemble release team

Week 1:

• [Release Lead] Finalize release schedule and team
• [Release Lead] Prepare main branch for development of the new release
• [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 6:

• [Release Lead] Cut the v1.4.2 release

Week 9:

• [Release Lead] Cut the v1.4.3 release

Week 11 to 12:

• [Release Lead] [Track] Bump dependencies

Week 13:

• [Release Lead] Cut the v1.5.0-beta.0 release
• [Release Lead] Cut the v1.4.4 release
• [Release Lead] Create a new GitHub milestone for the next release
• [Release Lead] cut issues to providers to inform them to test against 1.5.0

Week 14:

• [Release Lead] Cut the v1.5.0-beta.1 release
• [Release Lead] Select release lead for the next release cycle

Week 15:

• [Release Lead] Create the release-1.5 release branch
• [Release Lead] Cut the v1.5.0-rc.0 release
• [CI Manager] Setup jobs and dashboards for the release-1.4 release branch
• [Communications Manager] Ensure the book for the new release is available

Week 15 to 17:

• [Communications Manager] Polish release notes

Week 16:

• [Release Lead] Cut the v1.5.0-rc.1 release

Week 17:

• [Release Lead] Cut the v1.5.0 release
• [Release Lead] Cut the v1.4.6 release
• [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

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
• [CI Manager] Bug triage
• [CI Manager] Maintain and improve release automation, tooling & related developer docs

If and when necessary:

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

[joekr]

/assign @joekr

[joekr]

/triage accepted

[sbueringer]

@joekr Follow-up to Wednesday. I also checked "Remove previously deprecated code". I think we're fine for this release

[Prajyot-Parab]

[Communications Manager] Ensure the book for the new release is available
PR - kubernetes/k8s.io#5541

[sbueringer]

Updated the tasks above.

[sbueringer]

All done, thx everyone!

/close

(let me know if we missed something)

[k8s-ci-robot]

@sbueringer: Closing this issue.

In response to this:

All done, thx everyone!

/close

(let me know if we missed something)

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/test-infra repository.

[chrischdi]

/reopen

I think we missed some parts in the release-tasks.md:

• Update supported versions
  
  • Which should be similar to what was done in 📖 docs: update CAPI support and guarantees #8308 .
• the table in CONTRIBUTING.md should also get an update.

I think we could also improve our release-tasks docs for this two points :-)

cc @furkatgofurov7 (as current release lead)

[k8s-ci-robot]

@chrischdi: Reopened this issue.

In response to this:

/reopen

I think we missed some parts in the release-tasks.md:

• Update supported versions
  
• Which should be similar to what was done in 📖 docs: update CAPI support and guarantees #8308 .
• the table in CONTRIBUTING.md should also get an update.

I think we could also improve our release-tasks docs for this two points :-)

cc @furkatgofurov7 (as current release lead)

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/test-infra repository.

[furkatgofurov7]

/reopen

I think we missed some parts in the release-tasks.md:

• Update supported versions
  

  • Which should be similar to what was done in 📖 docs: update CAPI support and guarantees #8308 .

• the table in CONTRIBUTING.md should also get an update.

cc @furkatgofurov7 (as current release lead)

@chrischdi thanks for spotting this, there is an open PR already that tackles both of these for 1.6 release cycle: https://github.com/kubernetes-sigs/cluster-api/pull/9119/files.

Have not gone through it yet, but I think we could make sure that, missing parts for 1.5 could be also covered in the same PR.

I think we could also improve our release-tasks docs for this two points :-)

+1.
/cc @g-gaston FYI

[fabriziopandini]

Should this be closed now?

[furkatgofurov7]

@chrischdi can we close it, your points should be covered now in #9119?

[joekr]

If not now we will be sure to close it at our meeting to discuss the v1.6 release tasks.

[furkatgofurov7]

/close

[k8s-ci-robot]

@furkatgofurov7: Closing this issue.

In response to this:

/close

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/test-infra repository.