-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Comments
cc @kubernetes-sigs/cluster-api-release-team |
/triage accepted |
@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. |
can we use milestone? |
+1 for using release milestone |
+1 as well |
@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. |
@sbueringer I must have missed this. It will be fixed. Thank you for pointing it out. |
Thx! Probably because v1.4 is the first time we create this doc.
|
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? |
Not sure, but we probably find most when we look over the generated release notes when we write the final release notes |
cc @ykakarap ^ is:
Edit: Both merged and new jobs are available in https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api-1.4. Edit2: (follow-up) removal of release-1.1 branch jobs:
|
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. |
The release retrospective was organized on March 30th. With this the v1.4.0 release cycle is complete. Closing the issue. /close |
@ykakarap: Closing this issue. In response to this:
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. |
Please see the corresponding section in release-tasks.md for documentation of individual tasks.
Tasks
Notes:
Week -3 to 1:
Week 1:
Week 1 to 4:
Week 6:
Week 9:
Week 11 to 12:
Week 13:
Week 14:
Week 15 (Code Freeze):
Week 15 to 17:
Week 16:
Week 17:
Continuously:
If and when necessary:
The text was updated successfully, but these errors were encountered: