-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Review components to give users an indication of the level of support #9377
Comments
The information to be captured:
|
The definition for stability should include:
|
To be done/discuss: add template for components to fill out (#9412 (comment)) |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
As we do in the core component, we should label the components in the contrib repository to give users an insight as to what components are planned on being supported for the long term, versus which are experimental.
This requires a definition of what experimental, alpha, beta, stable for components in contrib. This would also need a dimension to specify components supported by a vendor.
Sub-tasks:
The text was updated successfully, but these errors were encountered: