Policies for stability #18
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced May 29, 2022
nightkr
reviewed
May 29, 2022
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
6 tasks
Signed-off-by: clux <[email protected]> link to future stability policy discussion Signed-off-by: clux <[email protected]> create a kubernetes versioning matrix now since we can't use kubernetes versioning post 1.0, there's no point waiting. let's define and get clarity now. Signed-off-by: clux <[email protected]> potential solution for kubernetes version policy Propose a 5 version range from [MAX-4, MAX], since this matches kubernetes upstream support. This will need to go with better e2e tests. Signed-off-by: clux <[email protected]> remove kubernetes doc - moved into #19 Signed-off-by: clux <[email protected]> update with unstable features Signed-off-by: clux <[email protected]>
|
Updated to reflect reality. I think this would be a good thing to have because most of this actually reflects how we approach things (in particular w.r.t. deprecations/unstable features/interface changes/platform support). It would be enough for us to change us to a "Stable Client" modulo the upstream requirements (which granted, are looser than no semver breaking changes). Feedback on particular points here would be appreciated. This has sat here for too long and I hope it's not super controversial (although i expect there may be some points on the 1.0 stuff in there). |
nightkr
approved these changes
Mar 5, 2023
Signed-off-by: clux <[email protected]>
kazk
approved these changes
Mar 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Policies for stability that is sufficient to meet
according to the client requirements even though we are not 1.0.
This documents:
this will mark most of the remaining checks on kube-rs/kube#726 as completed and will let us move out any remaining issues into more focused issues.