Difference between 0.x and 1.x versions and support plan
Closed this issue · 8 comments
Awhile back there were some CVEs which popped up from downstream projects using the 0.x version but was fixed/patched in the 1.x version and this brought up the question: What is the difference between these two versions and is the long-term plan to support both 0.x and 1.x releases? How might one prepare to migrate from 0.x to 1.x version?
Please forgive me if I missed this somewhere in the documentation...
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
I'd be open to help with a PR to contribute here, but not even sure where I could go to get these answers (e.g. a community meeting, etc.).
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The apimachinery repo / module only has v0.x.y tags.
v0.x.y of this repo corresponds to v1.x.y of kubernetes/kubernetes. Any CVE associated with this module must be reported using v0 tag ranges
/close
@liggitt: Closing this issue.
In response to this:
/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-sigs/prow repository.
Thanks! I see now. The v1.x.y tags are even the exact same commit as the corresponding v0.x.y tag. I'm guessing the dev CI process just has extra "tag waste".