-
Notifications
You must be signed in to change notification settings - Fork 468
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
Document v1alpha1 deprecation timeline #906
Comments
I think we should do two docs update to communicate:
Mixing minor releases with API version releases is a bit confusing (maybe because that is new?). |
There is no such thing as Deprecation for alphas. |
Yeah I do get that, but I don't think we can always tie removal of API versions with introduction of newer API versions. At some point, there will be no more new API versions to add. I think we're roughly trying to follow Kubernetes versioning guidelines which do include additions and removals of APIs along with minor k8s releases. Unfortunately I'm not seeing any clear upstream documentation for the relationship between API groups/versions and Kubernetes versions (looking at https://kubernetes.io/releases/version-skew-policy/ and https://github.com/kubernetes/community/blob/master/contributors/design-proposals/release/versioning.md#kubernetes-release-versioning). We likely need clearer documentation around how this works though, at least for Gateway API. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
With v1alpha2 released and v1alpha1 effectively frozen, we should document how long v1alpha1 will continue to exist in this repo. Maybe we should announce deprecation now + the plan to formally remove the API version from the repo in our next minor release (v0.5.0).
A big thanks to @ccfishk for originally raising this in #903 (comment)!
The text was updated successfully, but these errors were encountered: