Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tasks for v1.4 release cycle #7672

Closed
27 of 31 tasks
ykakarap opened this issue Nov 30, 2022 · 15 comments
Closed
27 of 31 tasks

Tasks for v1.4 release cycle #7672

ykakarap opened this issue Nov 30, 2022 · 15 comments
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@ykakarap
Copy link
Contributor

ykakarap commented Nov 30, 2022

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

Tasks

Notes:

  • Weeks are only specified to give some orientation.

Week -3 to 1:

Week 1:

Week 1 to 4:

Week 6:

Week 9:

Week 11 to 12:

  • [Release Lead] [Track] Bump dependencies
    • Note: This will probably be taken care by dependabot automation (controller-runtime will need a manual bump).

Week 13:

Week 14:

Week 15 (Code Freeze):

Week 15 to 17:

Week 16:

Week 17:

Continuously:

If and when necessary:

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Nov 30, 2022
@ykakarap ykakarap changed the title Tasks for v<release-tag> release cycle Tasks for v1.4 release cycle Nov 30, 2022
@ykakarap
Copy link
Contributor Author

cc @kubernetes-sigs/cluster-api-release-team

@fabriziopandini
Copy link
Member

/triage accepted
it is awesome to see this work kicking off...

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 30, 2022
@oscr
Copy link
Contributor

oscr commented Dec 13, 2022

@ykakarap Maybe it would be useful to have 1.4 release specific label(s) on the issues related to this release? I'm thinking it might be nice to be able to quickly find any and all release specific issues.

@fabriziopandini
Copy link
Member

can we use milestone?

@furkatgofurov7
Copy link
Member

+1 for using release milestone

@cpanato
Copy link
Member

cpanato commented Dec 15, 2022

+1 as well

@sbueringer
Copy link
Member

sbueringer commented Dec 21, 2022

@oscr I think the goal of Add docs to collect release notes for users and migration notes for provider implementers was to add one doc for provider changes and one doc to track user facing changes.

As far as I can tell the PR only added the doc for providers.

@oscr
Copy link
Contributor

oscr commented Dec 22, 2022

@sbueringer I must have missed this. It will be fixed. Thank you for pointing it out.

@sbueringer
Copy link
Member

sbueringer commented Dec 22, 2022

Thx! Probably because v1.4 is the first time we create this doc.

The goal of this task is to initially create the docs so that we can continuously add notes going forward. The release notes doc will be used to collect release notes during the release cycle and will be eventually used to write the final release notes. The provider migration doc is part of the book and contains instructions for provider authors on how to adopt to the new Cluster API version.

@ykakarap
Copy link
Contributor Author

Just trying to track what needs to go into the user facing changes doc. Looks like we have at least one item: #7955 (comment). Do we have a list of any other items that need to go into this doc?

@sbueringer
Copy link
Member

Not sure, but we probably find most when we look over the generated release notes when we write the final release notes

@furkatgofurov7
Copy link
Member

furkatgofurov7 commented Mar 13, 2023

@sbueringer
Copy link
Member

sbueringer commented Mar 14, 2023

Fyi I created the release branch together with Killian.

From now on we have to cherry-pick PRs if they should make it into 1.4.x

Killian will open a pr for the milestone applier.

@ykakarap
Copy link
Contributor Author

ykakarap commented Apr 7, 2023

The release retrospective was organized on March 30th.
Recording link: https://www.youtube.com/watch?v=4-6XJJ1ACdw (also linked in the release team meeting notes)

With this the v1.4.0 release cycle is complete.

Closing the issue.

/close

@k8s-ci-robot
Copy link
Contributor

@ykakarap: Closing this issue.

In response to this:

The release retrospective was organized on March 30th.
Recording link: https://www.youtube.com/watch?v=4-6XJJ1ACdw (also linked in the release team meeting notes)

With this the v1.4.0 release cycle is complete.

Closing the issue.

/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

7 participants