-
Notifications
You must be signed in to change notification settings - Fork 669
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
Kubernetes 1.26 Release #940
Comments
I'd like to take the pre-release code changes to become more familiar with the process. /assign |
Thanks @a7i, fyi all for this release I'd like to organize our tasks through a Github project so we can better keep track of what is in progress. I'm looking into how we can set one up for our project |
Yes, I saw your comment after the assignment. Makes sense 👍🏼 |
/unassign |
Got the project set up at https://github.com/orgs/kubernetes-sigs/projects/22 and filled in with draft issues Let's wrap up v0.25.0 first, and then we can start organizing those. It will be great if we can get a dedicated meeting time set up for this from #944 |
cool, looks more transparency and funny ~~ |
Last call: going to tag v0.26.0 this afternoon if there are no last minute changes waiting to get in (#1021) |
/close |
@a7i: 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. |
From https://github.com/kubernetes/sig-release/blob/master/releases/release-1.26/README.md:
The 1.26 release cycle is as follows:
Pre-release Code Changes
Before publishing each release, the following code updates must be made:
k8s.io
dependencies to the-rc
tags. These tags are usually published around upstream code freeze. Examplek8s.io
dependencies to GA tags once they are published (following the upstream release). ExampleThe text was updated successfully, but these errors were encountered: