Update some modifications on the release templates (opensearch-projec…

…t#1781)

Signed-off-by: Zelin Hao <[email protected]>

.github/ISSUE_TEMPLATE/release_template.md

@@ -31,17 +31,17 @@ To aid in understanding the state of the release there is a table with status in
 ### 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.
+- [ ] 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.
-- [ ] Declare a pencils down date for new features to be merged.
-- [ ] Finalize scope and feature set and update [the Public Roadmap](https://github.com/orgs/opensearch-project/projects/1).
-- [ ] [Create a version label](https://github.com/opensearch-project/opensearch-plugins/blob/main/META.md#create-or-update-labels-in-all-plugin-repos) in each component repo for this, and the next minor release.
+- [ ] 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-build/blob/main/meta/README.md#create-a-release-issue) that links 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)
 - [ ] Ensure that all release issues created above are assigned to an owner in the component team.
 
-### CI/CD - _Ends __REPLACE_RELEASE-minus-14-days___
+### CI/CD (Feature Freeze) - _Ends __REPLACE_RELEASE-minus-14-days__
 
 - [ ] Create Jenkins workflows that run daily snapshot builds for OpenSearch and OpenSearch Dashboards. 
 - [ ] Increment each component version to {{ env.VERSION }} and ensure working CI in component repositories.
@@ -53,21 +53,21 @@ __REPLACE with OpenSearch wide initiatives to improve quality and consistency.__
 
 ### Release testing - _Ends __REPLACE_RELEASE-minus-6-days___
 
-- [ ] Code Complete (__REPLACE_RELEASE-minus-14-days__ - __REPLACE_RELEASE-minus-11-days__): Teams test their component within the distribution, ensuring integration, backwards compatibility, and perf tests pass.
-- [ ] Sanity Testing (__REPLACE_RELEASE-minus-8-days__ - __REPLACE_RELEASE-minus-6-days__): Sanity testing and fixing of critical issues found by teams.
+- [ ] Declare a release candidate build, and provide the instructions with the release candidates for teams on testing (__REPLACE_RELEASE-minus-8-days__).
+- [ ] Sanity Testing (__REPLACE_RELEASE-minus-8-days__ - __REPLACE_RELEASE-minus-6-days__): Sanity testing and fixing of critical issues found by teams. Teams test their components within the distribution, ensuring integration, backwards compatibility, and perf tests pass.
+- [ ] Publish all test results in the comments of this issue.
 
 ### Performance testing validation - _Ends __REPLACE_RELEASE-minus-6-days___
+
 - [ ] Performance tests do not show a regression
 - [ ] Longevity tests do not show any issues
 
-
 ### Release - _Ends {__REPLACE_RELEASE-day}_
 
-- [ ] Declare a release candidate build, and publish all test results.
 - [ ] Verify [all issues labeled `v{{ env.VERSION }}` in all projects](https://github.com/opensearch-project/project-meta#find-labeled-issues) have been resolved.
 - [ ] Complete [documentation](https://github.com/opensearch-project/documentation-website) for this release.
 - [ ] Author [blog post](https://github.com/opensearch-project/project-website) for this release.
-- [ ] Gather, review and add release notes to the release branch. [git-release-notes](https://github.com/ariatemplates/git-release-notes) may be used to generate release notes from your commit history.
+- [ ] Gather, review and combine the release notes from components repositories. Create a PR for the merged release notes and ask PM teams to review it.
 - [ ] __REPLACE_RELEASE-minus-1-day - Publish this release on [opensearch.org](https://opensearch.org/downloads.html).
 - [ ] __REPLACE_RELEASE-day - Publish a [blog post](https://github.com/opensearch-project/project-website) - release is launched!
 

meta/templates/releases/release_template.md

@@ -1,21 +1,28 @@
-Coming from [opensearch-build__REPLACE_ISSUE_NUMBER__](https://github.com/opensearch-project/opensearch-build/issues/__REPLACE_ISSUE_NUMBER__), release version __REPLACE_MAJOR_MINOR__. Please follow the following checklist.
+This is a component issue for __{REPLACE_WITH_RELEASE_VERSION}__.
+Coming from [opensearch-build__REPLACE_ISSUE_NUMBER__](https://github.com/opensearch-project/opensearch-build/issues/__REPLACE_ISSUE_NUMBER__). Please follow the following checklist.
+__Please refer to the DATES in that post__.
 
 <details><summary>How to use this issue</summary>
 <p>
 
 ## This Component Release Issue
 
-This issue captures the state of the OpenSearch release for this component, its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help.  Any release related work can be linked to this issue or added as comments to create visiblity into the release status.
+This issue captures the state of the OpenSearch release, on component/plugin level; its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help. 
+Any release related work can be linked to this issue or added as comments to create visiblity into the release status.
+
+## Release Steps
+
+There are several steps to the release process; these steps are completed as the whole component release and components that are behind present risk to the release. The component owner resolves the tasks in this issue and communicate with the overall release owner to make sure each component are moving along as expected.
+
+Steps have completion dates for coordinating efforts between the components of a release; components can start as soon as they are ready far in advance of a future release. The most current set of dates is on the overall release issue linked at the top of this issue.
 
 ## The Overall Release Issue
 
 Linked at the top of this issue, the overall release issue captures the state of the entire OpenSearch release including references to this issue, the release owner which is the assignee is responsible for communicating the release status broadly.  Please contact them or @mention them on that issue for help.
 
-## Release Steps
-
-There are several steps to the release process, these steps are completed as the whole release and components that are behind present risk to the release.  The component owner completes the tasks in this issue which are monitored by the overall release owner to make sure all components are moving along as expected.
+## What should I do if my plugin isn't making any changes?
 
-Steps have completion dates for coordinating efforts between the components of a release; components can start as soon as they are ready far in advance of a future release.  The most current set of dates is on the overall release issue linked at the top of this issue.
+If including changes in this release, increment the version on `__{REPLACE_MAJOR_MINOR_PATCH}__` branch to `__{REPLACE_MAJOR_MINOR_PATCH}__` for Min/Core, and `__{REPLACE_MAJOR_MINOR_PATCH_0}__` for components. Otherwise, keep the version number unchanged for both.
 
 </p>
 </details>
@@ -24,38 +31,38 @@ Steps have completion dates for coordinating efforts between the components of a
 
 - [ ] Assign this issue to a release owner.
 - [ ] Finalize scope and feature set and update [the Public Roadmap](https://github.com/orgs/opensearch-project/projects/1).
+- [ ] All the tasks in this issue have been reviewed by the release owner.
 - [ ] Create, update, triage and label all features and issues targeted for this release with `v__REPLACE_MAJOR_MINOR_PATCH__`.
 
-### CI/CD - __REPLACE_DATE___
+### CI/CD
 
-- [ ] Check that the previous post-release action items incremented the version to `__REPLACE_MAJOR_MINOR_PATCH_BUILD__` and that CI is passing.
+- [ ] All code changes for `__{REPLACE_MAJOR_MINOR_PATCH}__` are complete.
+- [ ] Ensure working and passing CI.
 - [ ] Check that this repo is included in the [distribution manifest](https://github.com/opensearch-project/opensearch-build/blob/main/manifests/__REPLACE_MAJOR_MINOR_PATCH__).
 
 ### Pre-Release
 
-- [ ] Branch and build from a `__REPLACE_MAJOR_MINOR__` branch.
+- [ ] Update to the `__REPLACE_MAJOR_MINOR__` release branch in the [distribution manifest](https://github.com/opensearch-project/opensearch-build/blob/main/manifests/__REPLACE_MAJOR_MINOR_PATCH__).
 - [ ] Increment the version on the parent branch to the next development iteration.
-- [ ] Update your branch in the [manifest](https://github.com/opensearch-project/opensearch-build/blob/main/manifests/__REPLACE_MAJOR_MINOR_PATCH__) for this release.
+- [ ] Gather, review and publish release notes follwing the [rules](https://github.com/opensearch-project/opensearch-plugins/blob/main/RELEASE_NOTES.md) and back port it to the release branch.[git-release-notes](https://github.com/ariatemplates/git-release-notes) may be used to generate release notes from your commit history.
+- [ ] Confirm that all changes for `__{REPLACE_MAJOR_MINOR_PATCH}__` have been merged.
 - [ ] Add this repo to the [manifest](https://github.com/opensearch-project/opensearch-build/blob/main/manifests/) for the next developer iteration.
-- [ ] Feature complete, pencils down.
-- [ ] Fix bugs that target this release.
 
 ### Release Testing
 
-- [ ] Code Complete (__REPLACE_REPLACE_RELEASE-minus-14-days__ - __REPLACE_RELEASE-minus-11-days__): Test within the distribution, ensuring integration, backwards compatibility, and performance tests pass.
-- [ ] Sanity Testing (__REPLACE_REPLACE_RELEASE-minus-8-days__ - __REPLACE_RELEASE-minus-6-days__): Sanity testing *and* fixing of critical issues found.
+- [ ] Find/fix bugs using latest tarball and docker image provided in parent release issue and update the release notes if necessary.
+- [ ] Code Complete: Test within the distribution, ensuring integration, backwards compatibility, and performance tests pass.
+- [ ] Sanity Testing: Sanity testing *and* fixing of critical issues found.
+- [ ] File issues for all intermittent test failures.
 
 ### Release
 
 - [ ] Complete [documentation](https://github.com/opensearch-project/documentation-website).
-- [ ] Gather, review and publish release notes.
 - [ ] Verify all issued labeled for this release are closed or labelled for the next release.
 
 ### Post Release
 
-- [ ] Create [a release tag](https://github.com/opensearch-project/.github/blob/main/RELEASING.md#tagging).
-- [ ] Update the [manifest](https://github.com/opensearch-project/opensearch-build/blob/main/manifests/__REPLACE_MAJOR_MINOR_PATCH__) to use the release tag.
 - [ ] Prepare for an eventual security fix development iteration by incrementing the version on the release branch to the next eventual patch version.
 - [ ] Add this repo to the [manifest](https://github.com/opensearch-project/opensearch-build/blob/main/manifests/) of the next eventual security patch version.
 - [ ] [Suggest improvements](https://github.com/opensearch-project/opensearch-build/issues/new) to [this template](https://github.com/opensearch-project/opensearch-build/blob/main/meta/templates/releases/release_template.md).
-- [ ] Conduct a postmortem, and publish its results.
+- [ ] Conduct a retrospective, and publish its results.