Barani

Thanks for your feedback @reta . Please find my comments inline. > @bbarani thanks a lot for the proposal, I think this is a HUGE step in right direction, I...

> Thanks for documenting all of this the clarity is a great improvement - could you transform this issue's description into a pull request on the `RELEASING.md` so this is...

> > Thanks for documenting all of this the clarity is a great improvement - could you transform this issue's description into a pull request on the `RELEASING.md` so this...

> > Sure, we will add the summary, motivation along with roles and responsibilities to this [RELEASE_PROCESS_OPENSEARCH.md](https://github.com/opensearch-project/opensearch-build/blob/1499c472fec3d36bc0d3b30ffca8b08bb5a65c4d/RELEASE_PROCESS_OPENSEARCH.md) soon. CC: @prudhvigodithi > > @bbarani should this be part of the https://github.com/opensearch-project/.github/blob/main/RELEASING.md...

We will document the current security mechanism in place soon. CC: @prudhvigodithi @gaiksaya @zelinh

@nknize @dblock I will open a PR for RELEASE_PROCESS.md as mentioned in this [comment](https://github.com/opensearch-project/.github/issues/166#issuecomment-1585176486) soon.

@nknize I have opened a [RFC](https://github.com/opensearch-project/.github/issues/167) along with [PR](https://github.com/opensearch-project/opensearch-build/blob/1499c472fec3d36bc0d3b30ffca8b08bb5a65c4d/RELEASE_PROCESS_OPENSEARCH.md#opensearch-release-process) with the steps involved in release cycle process for OpenSearch releases.

@hpatro @madolson @zuiderkwast Is this change targeted for Valkey 8? If so, can we add it to Valkey 8 project [board](https://github.com/orgs/valkey-io/projects/2)?

> I was waiting on performance numbers from Hari before officially adding it. @hpatro Do you have performance numbers? Can you please add it to this issue to move forward...

> Yes, LGTM. Awesome! Thanks all.