Tag cluster & workspace as beta features in extension api #1589
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
Signed-off-by: Jari Kolehmainen <jari.kolehmainen@gmail.com>
jakolehm
added
area/extension
|
Cluster cleanup has been already started but it didn't make it into 4.0: #1435 |
Signed-off-by: Jari Kolehmainen <jari.kolehmainen@gmail.com>
Nokel81
reviewed
Dec 1, 2020
| /** | ||
| * Cluster | ||
| * | ||
| * @beta |
There was a problem hiding this comment.
This PR should probably have some doc describing what we mean by these markers and what guarantees (or not) they mean.
Nokel81
approved these changes
Dec 3, 2020
jakolehm
added a commit
that referenced
this pull request
Dec 7, 2020
* mark cluster & workspace as beta Signed-off-by: Jari Kolehmainen <jari.kolehmainen@gmail.com> * back to public Signed-off-by: Jari Kolehmainen <jari.kolehmainen@gmail.com>
Merged
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.
Both of those APIs still include internal details that we really have to cleanup. Tagging these as
betawill set better expectation level and also allows us to tweak these APIs within 4.x series (until we take the beta tag away).