opensearch-benchmark
opensearch-benchmark copied to clipboard
opensearch-project
[RFC] Introduce RELEASE issues in OpenSearch Benchmark to better track releases
Is your feature request related to a problem? Please describe.
The community would benefit from knowing when an OSB release is happening. Currently, the only way to know is to visit the roadmap. Based on our maintainer's guide, maintainers for OSB are required to remind the community a week prior that a code freeze will take place two days prior to the scheduled release.
Since we are releasing OSB on a monthly cadence and since not all users check OSB roadmap regularly, we should leverage a part of the repository that users mostly check to remind them of upcoming releases.
Describe the solution you'd like
Similar to the opensearch-build repository, we should leverage RELEASE issues. For example, see this issue for OpenSearch and OpenSearch Dashboards 2.13.0. These issues will be structured differently and contain information related to the release such as code freeze date, checklists for pre-release and post-release tasks, related PRs and issues, what changes are expected to be included, etc.
We can also leverage a slack bot or Github actions workflow that notifies the public slack community of when a code freeze will occur.
In the future, we can also have a dedicated page in the OpenSearch Benchmark's landing page, similar to OpenSearch's release schedule and maintenance policy,, that links the issue and code freeze dates.
+1 to the idea of creating release issue for OpenSearch benchmark release. Pre-planning the releases along with well defined code freeze date would help prioritize the changes in timely manner.
