-
Notifications
You must be signed in to change notification settings - Fork 36
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
Remove Experimental Tag From Search Comparison Tool #144
Comments
What do you think? @dagneyb @elfisher @lauralexis @dblock @macrakis |
This is the approach we're going to take. Moving this into "Next" in the project and removed "Proposal". |
We're delaying removal of the experimental tag until a later date. |
Wanted to clarify the original issue description
@noCharger made a good point in this comment on my previous attempt, For example, VizBuilder, another experimental OpenSearch Dashboards feature, uses Any suggestions/ideas on what to use for displaying the tool description, if at all? Is cc: @kgcreative |
What/Why
What are you proposing?
I believe that the comparison tool is stable and have no immediate plans to make changes to it. IMO, we should remove the experimental tag from the tool in an upcoming release.
What problems are you trying to solve?
We should try to minimize the amount of time anything is considered experimental.
What is the developer experience going to be?
None
Are there any security considerations?
No
Are there any breaking changes to the API
No
What is the user experience going to be?
I believe the "Experimental Feature" label should be removed, but the box it's in with the description, link to documentation, and forum should remain. https://searchapps.playground.opensearch.org/app/searchRelevance#/.
Are there breaking changes to the User Experience?
No
Why should it be built? Any reason not to?
Experimental features are meant for features that are not ready for production due to potential API changes or performance concerns. This feature has neither of those concerns.
What will it take to execute?
The text was updated successfully, but these errors were encountered: