New release template

Signed-off-by: Prudhvi Godithi <pgodithi@amazon.com>

.github/ISSUE_TEMPLATE/release_template.md

@@ -28,23 +28,21 @@ To aid in understanding the state of the release there is a table with status in
 </p>
 </details>
 
-### Preparation
+### [Preparation](https://github.com/prudhvigodithi/opensearch-build/blob/public/RELEASE_PROCESS_OPENSEARCH.md#preparation)
 
 - [ ] Assign this issue to a release owner.
 - [ ] Declare a pencils down date for new features to be merged. 
 - [ ] __REPLACE_RELEASE-minus-14-days__ is pencils down date for feature freeze.
-- [ ] Update the Campaigns section to include monitoring campaigns during this release. 
 - [ ] Update this issue so all `__REPLACE_RELEASE-__` placeholders have actual dates.
-- [ ] Document any new quality requirements or changes.
-- [ ] Finalize scope and feature set and update [the Public Roadmap](https://github.com/orgs/opensearch-project/projects/1). 
-- [ ] [Create a release issue in every component repo](https://github.com/opensearch-project/opensearch-plugins/blob/main/META.md#create-an-issue-in-all-plugin-repos) based on [component release issue template](https://github.com/opensearch-project/opensearch-build/blob/main/.github/ISSUE_TEMPLATE/component_release_template.md) and link back to this issue, update Components section with these links.
-- [ ] Ensure the label is created in each component repo for this new version, and the next minor release. [Create a version label](https://github.com/opensearch-project/opensearch-plugins/blob/main/META.md#create-or-update-labels-in-all-plugin-repos)
+- [ ] Existence of label in each component repo. For more information check 
 - [ ] Ensure that all release issues created above are assigned to an owner in the component team.
 - [ ] Increase the build frequency for the this release from once a day (H 1 * * *) to once every hour (H/60 * * * *) in [jenkinsFile](https://github.com/opensearch-project/opensearch-build/blob/main/jenkins/check-for-build.jenkinsfile).
 
 ### Campaigns
 
-__REPLACE with OpenSearch wide initiatives to improve quality and consistency.__
+- [ ] [Create a release issue in every component repo](https://github.com/opensearch-project/opensearch-plugins/blob/main/META.md#create-an-issue-in-all-plugin-repos) based on [component release issue template](https://github.com/opensearch-project/opensearch-build/blob/main/.github/ISSUE_TEMPLATE/component_release_template.md) and link back to this issue, update Components section with these links.
+- [ ] Update the campaign section to include the component level release issues. For more information check the [campaigns](https://github.com/prudhvigodithi/opensearch-build/blob/public/RELEASE_PROCESS_OPENSEARCH.md#campaigns) section.
+
 
 ### Release Branch - _Ends __REPLACE_RELEASE-minus-14-days__
 
@@ -116,4 +114,4 @@ __Replace with links to all component tracking issues.__
 | :red_circle: | Missed multiple milestones |
 
 </p>
-</details>
+</details>

README.md

@@ -7,56 +7,55 @@
 
 - [Releasing OpenSearch](#releasing-opensearch)
   - [Releases and Versions](#releases-and-versions)
-  - [Creating a New Version](#creating-a-new-version)
-  - [Onboarding a New Plugin](#onboarding-a-new-plugin)
-  - [Building and Testing an OpenSearch Distribution](#building-and-testing-an-opensearch-distribution)
-    - [Building from Source](#building-from-source)
-    - [Assembling a Distribution](#assembling-a-distribution)
-    - [Building Patches](#building-patches)
-    - [Min snapshots](#min-snapshots)
-    - [CI/CD Environment](#cicd-environment)
-    - [Build Numbers](#build-numbers)
-    - [Latest Distribution Url](#latest-distribution-url)
-    - [Testing the Distribution](#testing-the-distribution)
-    - [Checking Release Notes](#checking-release-notes)
-    - [Signing Artifacts](#signing-artifacts)
-      - [PGP](#pgp)
-      - [Windows](#windows)
-    - [Signing RPM artifacts](#signing-rpm-artifacts)
-  - [Making a Release](#making-a-release)
-    - [Releasing for Linux](#releasing-for-linux)
-    - [Releasing for FreeBSD](#releasing-for-freebsd)
-    - [Releasing for Windows](#releasing-for-windows)
-    - [Releasing for MacOS](#releasing-for-macos)
-  - [Utilities](#utilities)
-    - [Checking Out Source](#checking-out-source)
-    - [Cross-Platform Builds](#cross-platform-builds)
-    - [Sanity Checking the Bundle](#sanity-checking-the-bundle)
-    - [Auto-Generating Manifests](#auto-generating-manifests)
-  - [Deploying Infrastructure](#deploying-infrastructure)
+  - [Release labels](#release-labels)
+- [Onboarding a New Plugin](#onboarding-a-new-plugin)
+- [Building and Testing an OpenSearch Distribution](#building-and-testing-an-opensearch-distribution)
+  - [Building from Source](#building-from-source)
+  - [Assembling a Distribution](#assembling-a-distribution)
+  - [Building Patches](#building-patches)
+  - [Min snapshots](#min-snapshots)
+  - [CI/CD Environment](#cicd-environment)
+  - [Build Numbers](#build-numbers)
+  - [Latest Distribution Url](#latest-distribution-url)
+  - [Testing the Distribution](#testing-the-distribution)
+  - [Checking Release Notes](#checking-release-notes)
+  - [Signing Artifacts](#signing-artifacts)
+    - [PGP](#pgp)
+    - [Windows](#windows)
+  - [Signing RPM artifacts](#signing-rpm-artifacts)
+- [Making a Release](#making-a-release)
+  - [Releasing for Linux](#releasing-for-linux)
+  - [Releasing for FreeBSD](#releasing-for-freebsd)
+  - [Releasing for Windows](#releasing-for-windows)
+  - [Releasing for MacOS](#releasing-for-macos)
+- [Utilities](#utilities)
+  - [Checking Out Source](#checking-out-source)
+  - [Cross-Platform Builds](#cross-platform-builds)
+  - [Sanity Checking the Bundle](#sanity-checking-the-bundle)
+  - [Auto-Generating Manifests](#auto-generating-manifests)
+- [Deploying Infrastructure](#deploying-infrastructure)
 - [Contributing](#contributing)
 - [Getting Help](#getting-help)
 - [Code of Conduct](#code-of-conduct)
 - [Security](#security)
 - [License](#license)
 - [Copyright](#copyright)
 
-## Releasing OpenSearch
+### Releasing OpenSearch
 
-### Releases and Versions
+See [release process](./RELEASE_PROCESS_OPENSEARCH.md) document for more information.
+
+#### Releases and Versions
 
 The OpenSearch project releases as versioned distributions of OpenSearch, OpenSearch Dashboards, and the OpenSearch plugins. It [follows semantic versioning](https://opensearch.org/blog/technical-post/2021/08/what-is-semver/). Software, such as Data Prepper, clients, and the Logstash output plugin, are versioned independently of the OpenSearch Project. They also may have independent releases from the main project distributions. The OpenSearch Project may also release software under alpha, beta, release candidate, and generally available labels. The definition of when to use these labels is derived from [the Wikipedia page on Software release lifecycle](https://en.wikipedia.org/wiki/Software_release_life_cycle). Below is the definition of when to use each label.
 
-Release labels:
+#### Release labels:
 
 * **Alpha** - The code is released with instructions to build. Built distributions of the software may not be available. Some features many not be complete. Additional testing and developement work is planned. Distributions will be postfixed with `-alphaX` where "X" is the number of the alpha version  (e.g., "2.0-alpha1").
 * **Beta** - Built distributions of the software are available. All features are completed. Additional testing and developement work is planned. Distributions will be postfixed with `-betaX` where "X" is the number of the beta version  (e.g., "2.0.0-beta1").
 * **Release Candidate** - Built distributions of the software are available. All features are completed. Code is tested and minimal validation remains. At this stage the software is potentially stable and will release unless signficant bugs emerge. Distributions will be postfixed with `-rcX` where "X" is the number of the release candidate version (e.g., "2.0.0-rc1").
 * **Generally Available** - Built distributions of the software are available. All features are completed and documented. All testing is completed. Distributions for generally available versions are not postfixed with an additional label (e.g., "2.0.0").
 
-### Creating a New Version
-
-Each new OpenSearch release process starts when any one component increments a version, typically on the `main` branch. For example, [OpenSearch#1192](https://github.com/opensearch-project/OpenSearch/pull/1192) incremented the version to 2.0. The [version check automation workflow](.github/workflows/versions.yml) will notice this change or it can be triggered [manually](https://github.com/opensearch-project/opensearch-build/actions/workflows/versions.yml), and make a pull request (e.g. [opensearch-build#514](https://github.com/opensearch-project/opensearch-build/pull/514)) that adds a new manifest (e.g. [opensearch-2.0.0.yml](manifests/2.0.0/opensearch-2.0.0.yml). After that's merged, a GitHub issue is automatically opened by [this workflow](.github/workflows/releases.yml) to make a new release using [this release template](.github/ISSUE_TEMPLATE/release_template.md) (e.g. [opensearch-build#566](https://github.com/opensearch-project/opensearch-build/issues/566)). Existing and new components [(re)onboard into every release](ONBOARDING.md) by submitting pull requests to each version's manifest.
 
 ### Onboarding a New Plugin
 
@@ -210,9 +209,10 @@ RPM artifacts are signed via a legacy shell script which uses a [macros template
 
 See [src/sign_workflow](./src/sign_workflow) for more information.
 
+
 ### Making a Release
 
-#### Releasing for Linux / Windows
+#### Releasing for Linux and Windows
 
 The Linux / Windows release is managed by a team at Amazon following [this release template](.github/ISSUE_TEMPLATE/release_template.md) (e.g. [opensearch-build#2649](https://github.com/opensearch-project/opensearch-build/issues/2649)).
 
@@ -277,6 +277,7 @@ Check for updates and create any new manifests.
 
 See [src/manifests_workflow](./src/manifests_workflow) for more information.
 
+
 ### Deploying Infrastructure
 
 Storage and access roles for the OpenSearch release process are codified in a [CDK project](./deployment/README.md).