You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
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: