-
Notifications
You must be signed in to change notification settings - Fork 483
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
[Feature Request] OpenSearch Benchmark dedicated release page #3409
Comments
Thanks for opening this after our discussion @IanHoang - I think this is an interesting idea that could benefit the community. @nateynateynate @kaimmej - let's add talk about this in an upcoming planning meeting |
This was briefly discussed during the public operations meeting last week and seems like it would be a good idea. @krisfreedain do we need to wait for feedback from @natebower and @kaimmej? |
[Catch All Triage - 1, 2, 3, 4] |
@IanHoang - put together a proposed outline for the page - I would recommend basing it off of an existing one, like the mentioned releases page. We can then talk through where it would make sense in the menu, who updates the information, what is listed on the page, etc. |
@krisfreedain here is the proposed outline for the page: https://docs.google.com/document/d/1TBWht1_fKtm_yAiMA6d3qod2KfJ8QNtTXCd1-EguUXc/edit?tab=t.0
Maintainers of OSB could update the information and what's listed on the page. Let me know your thoughts? |
Is your feature request related to a problem? Please describe
Many of our users are interested in knowing when the next release is since they plan implementing their changes around OSB's release schedule.
To keep the community updated on OSB's next minor release, we initially created and pinned release issues (example here) to the top of the issues section of our repository. We eventually switched to pinning a single issue that serves as a schedule. But after some thought, we think it would be better for the community if we had a public release page.
Describe the solution you'd like to see
Instead of keeping track of our releases in an issue on OSB, we'd like to surface it on OpenSearch.org similar to OpenSearch's public release calendar.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: