-
Notifications
You must be signed in to change notification settings - Fork 163
Spruce up availability guidance #594
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
Conversation
### What the badges mean | ||
|
||
Features may have different availability states between: | ||
Each badge provides up to three key pieces of information: |
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.
not all versioning is implemented through badges. I recommend that we keep the explanation of the lifecycle and versions and the badge info/examples separate
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.
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.
one more nitpick, then good to go!
Co-authored-by: shainaraskas <[email protected]>
https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/594/get-started/versioning-availability#understanding-availability-in-the-docs