Sarat Vemulapalli

Thanks @lukas-vlcek for opening this one. I think it was originally authored to publish opensearch-project plugin zips. But the ask makes a lot of sense. @prudhvigodithi @reta do you think...

Gradle check is failing because we didn't merge the changes for 2.2. ``` * What went wrong: Execution failed for task ':distribution:bwc:staged:buildBwcLinuxTar'. > Building 2.2.0 didn't generate expected file /var/jenkins/workspace/gradle-check/search/distribution/bwc/staged/build/bwc/checkout-2.2/distribution/archives/linux-tar/build/distributions/opensearch-min-2.2.0-SNAPSHOT-linux-x64.tar.gz...

I've merged the changes from `main` to `feature/extensions`. Could you re-base and that should get gradle green.

@tlfeng looks like we do have few changes reverted, so is it safe to assume we will not ship in 2.1.0? I'll slap 2.2.0 label, let me know if you...

@anasalkouz this issue is tagged 2.1.0. We are code freeze for 2.1. I'll move this issue to 2.2.0, let me know if you think otherwise.

> Does this Github action have the provision to separate out the commits into different sections like Feature, Bugs, Enhancement, Documentation etc? I would like to have something like this...

Looks like the release drafter doesn't support multiple release branches i.e we cannot have different release notes for each of the release branch. Ref: https://github.com/release-drafter/release-drafter/issues/844

Created notes for RC1 using https://github.com/ariatemplates/git-release-notes. It doesnt automate the drafter, doesn't categorize labels but atleast an easier way to generate them once per release. We can continue to scout...

Posting comments from the PR to here: "I would ideally love something like: Category: PR title (#number) PR description Authored by abc@ Lets work on this for the next release....

> Have we considered creating a changelog as well? As a maintainer of other repositories, changelogs are so much easier to parse/search when dealing with version bumps/upgrades than individual release...