-
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
🌱 Provide faster support for new k8s minor releases #9971
🌱 Provide faster support for new k8s minor releases #9971
Conversation
+1 I think it would be great if we would allow our users to quickly pick up a new Kubernetes version with Cluster API! /lgtm |
LGTM label has been added. Git tree hash: af045fac8f8523cebddd1faeda7384e80a8d01b7
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/cc @kubernetes-sigs/cluster-api-release-team |
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Looks good! /lgtm As it was brought up in office hours this week. Maybe lazy consensus until next week Friday and then merge it? |
LGTM label has been added. Git tree hash: 15b58e9ac4a3187191754a8c430c2d13ebc47ae9
|
Make sense to me, I will give also another heads-up in office hours this week (two days before the deadline) |
/lgtm |
As per CAPI office hours, lazy consensus expires Jan 19th |
/approve /hold cancel |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I open a cherry-pick PR (#10024) |
What this PR does / why we need it:
Considering the maturity of the release process and the maturity of the process we are using to validate support for new Kubernetes releases, I would like to propose the introduction in our release schedule of a new "extra" patch release to be created approximately one week after a new Kubernetes minor release is available.
This will ensure the project will quickly provide official support for new Kubernetes releases to Cluster API users.
Additionally, this PR clarifies the 4-month cadence which we are de-facto using (mostly a cleanup of leftovers from previous versions).
/area release
/hold
For discussion in the next office hours meeting