You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: .github/ISSUE_TEMPLATE/release_template.md
+101-61
Original file line number
Diff line number
Diff line change
@@ -13,90 +13,130 @@ I noticed that a manifest was automatically created in [manifests/{{ env.VERSION
13
13
14
14
## This Release Issue
15
15
16
-
This issue captures the state of the OpenSearch release, its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help. There are linked issues on components of the release where individual components can be tracked. More details are included in the Maintainers [Release owner](https://github.com/opensearch-project/opensearch-build/blob/main/MAINTAINERS.md#release-owner) section.
16
+
This issue captures the state of the OpenSearch release, its assignee (Release Manager) is responsible for driving the release. Please contact them or @mention them on this issue for help. There are linked issues on components of the release where individual components can be tracked. For more information check the the [Release Process OpenSearch Guide](https://github.com/opensearch-project/opensearch-build/blob/public/RELEASE_PROCESS_OPENSEARCH.md).
17
17
18
-
## Release Steps
18
+
</p>
19
+
</details>
19
20
20
-
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 release owner completes the tasks in this ticket, whereas component owners resolve tasks on their ticket in their repositories.
21
+
Please refer to the following link for the release version dates: [Release Schedule and Maintenance Policy](https://opensearch.org/releases.html).
21
22
22
-
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.
-[ ] Existence of label in each component repo. For more information check the [release-label](https://github.com/opensearch-project/opensearch-build/blob/public/RELEASE_PROCESS_OPENSEARCH.md#release-label) section.
27
+
-[ ][Increase the build frequency](https://github.com/opensearch-project/opensearch-build/blob/public/RELEASE_PROCESS_OPENSEARCH.md#increase-the-build-frequency).
To aid in understanding the state of the release there is a table with status indicating each component state. This is updated based on the status of the component issues.
### [Release Branch and Version Increment](https://github.com/opensearch-project/opensearch-build/blob/public/RELEASE_PROCESS_OPENSEARCH.md#release-branch-readiness) - _Ends __REPLACE_RELEASE-minus-14-days__
32
36
33
-
-[ ] Assign this issue to a release owner.
34
-
-[ ] Declare a pencils down date for new features to be merged.
35
-
-[ ]__REPLACE_RELEASE-minus-14-days__ is pencils down date for feature freeze.
36
-
-[ ] Update the Campaigns section to include monitoring campaigns during this release.
37
-
-[ ] Update this issue so all `__REPLACE_RELEASE-__` placeholders have actual dates.
38
-
-[ ] Document any new quality requirements or changes.
39
-
-[ ] Finalize scope and feature set and update [the Public Roadmap](https://github.com/orgs/opensearch-project/projects/1).
40
-
-[ ][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.
41
-
-[ ] 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)
42
-
-[ ] Ensure that all release issues created above are assigned to an owner in the component team.
43
-
-[ ] 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).
-[ ][Components Version Increment](https://github.com/opensearch-project/opensearch-build/blob/public/RELEASE_PROCESS_OPENSEARCH.md#components-version-increment).
-[ ] All component repos create `<MajorVersion>.<MinorVersion>` branch for the release.
48
+
-[ ] Mark this as done once the [Code Complete](https://github.com/opensearch-project/opensearch-build/blob/public/RELEASE_PROCESS_OPENSEARCH.md#code-complete-and-feature-freeze) is reviewed.
49
+
-[ ] Create/Verify pull requests to add each component to relase input [manifests/{{ env.VERSION }}/opensearch-{{ env.VERSION }}.yml](/opensearch-project/opensearch-build/tree/main/manifests/{{ env.VERSION }}/opensearch-{{ env.VERSION }}.yml) and [manifests/{{ env.VERSION }}/opensearch-dashboards-{{ env.VERSION }}.yml](/opensearch-project/opensearch-build/tree/main/manifests/{{ env.VERSION }}/opensearch-dashboards-{{ env.VERSION }}.yml).
### [Release Candidate Creation and Testing](https://github.com/opensearch-project/opensearch-build/blob/public/RELEASE_PROCESS_OPENSEARCH.md#release-candidate-creation-and-testing) - _Ends __REPLACE_RELEASE-minus-6-days___
57
52
58
-
-[ ] OpenSearch / OpenSearch-Dashboards core and components teams finalize their features.
59
-
-[ ] Create Jenkins workflows that run daily snapshot builds for [OpenSearch](https://build.ci.opensearch.org/job/distribution-build-opensearch/) and [OpenSearch Dashboards](https://build.ci.opensearch.org/job/distribution-build-opensearch-dashboards/).
60
-
-[ ] Make pull requests to add each component to [manifests/{{ env.VERSION }}/opensearch-{{ env.VERSION }}.yml](/opensearch-project/opensearch-build/tree/main/manifests/{{ env.VERSION }}/opensearch-{{ env.VERSION }}.yml) and [manifests/{{ env.VERSION }}/opensearch-dashboards-{{ env.VERSION }}.yml](/opensearch-project/opensearch-build/tree/main/manifests/{{ env.VERSION }}/opensearch-dashboards-{{ env.VERSION }}.yml) with the corresponding checks.
-[ ][Broadcast and Communication](https://github.com/opensearch-project/opensearch-build/blob/public/RELEASE_PROCESS_OPENSEARCH.md#broadcast-and-communication).
-[ ] Code Complete: Make sure that the code for this specific version of the release is ready and the branch corresponding to this release has been added to this release version manifest.
65
-
-[ ] Verify pull requests to add each component to [manifests/{{ env.VERSION }}/opensearch-{{ env.VERSION }}.yml](/opensearch-project/opensearch-build/tree/main/manifests/{{ env.VERSION }}/opensearch-{{ env.VERSION }}.yml) and [manifests/{{ env.VERSION }}/opensearch-dashboards-{{ env.VERSION }}.yml](/opensearch-project/opensearch-build/tree/main/manifests/{{ env.VERSION }}/opensearch-dashboards-{{ env.VERSION }}.yml) have been merged.
66
-
-[ ] Gather, review and combine the release notes from components repositories.
-[ ] Declare a release candidate build, and provide the instructions with the release candidates for teams on testing (__REPLACE_RELEASE-minus-8-days__).
71
-
-[ ] Stop builds for this version of OpenSearch and/or OpenSearch Dashboards in order to avoid accidental commits going in unknowingly. Restart only if necessary else manually run the build workflow and declare new release candidate.
72
-
-[ ] After generate the release candidates, raise PR to lock input manifest refs of both OS and OSD builds with the commit ids from distribution manifest of the release candidates.
73
-
-[ ] 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.
74
-
-[ ] Publish all test results in the comments of this issue.
-[ ][Collaboration with the Project Management Team](https://github.com/opensearch-project/opensearch-build/blob/public/RELEASE_PROCESS_OPENSEARCH.md#collaboration-with-the-project-management-team).
-[ ] Verify [all issues labeled `v{{ env.VERSION }}` in all projects](https://github.com/opensearch-project/project-meta#find-labeled-issues) have been resolved.
84
-
-[ ] Complete [documentation](https://github.com/opensearch-project/documentation-website) for this release.
85
-
-[ ] Author [blog post](https://github.com/opensearch-project/project-website) for this release.
86
-
-[ ]__REPLACE_RELEASE-minus-1-day - Publish this release on [opensearch.org](https://opensearch.org/downloads.html).
87
-
-[ ]__REPLACE_RELEASE-day - Publish a [blog post](https://github.com/opensearch-project/project-website) - release is launched!
88
+
### Pre-Release activities
89
+
-[ ] Promote Repos.
90
+
--[ ] OS
91
+
--[ ] OSD
92
+
-[ ] Promote Artifacts.
93
+
--[ ] Windows
94
+
--[ ] Linux Debian
95
+
--[ ] Linux RPM
96
+
--[ ] Linux TAR
97
+
-[ ] Consolidated Release Notes.
98
+
99
+
### Release activities
100
+
-[ ] Docker Promotion.
101
+
-[ ] Release Validation part 1.
102
+
--[ ] OpenSearch and OpenSearch Dashboard Validation.
103
+
--[ ] Validate the native plugin installation.
104
+
-[ ] Merge consolidated release notes PR.
105
+
-[ ] Website and Documentation Changes.
106
+
--[ ] Merge staging website PR.
107
+
--[ ] Promote the website changes to prod.
108
+
--[ ] Add website alert.
109
+
-[ ] Release Validation part 2.
110
+
--[ ] Validate the artifact download URL's and signatures.
111
+
-[ ] Release Validation part 3.
112
+
--[ ] Trigger the validation build (Search for `Completed validation for <>` in the logs).
113
+
-[ ] Maven Promotion.
114
+
-[ ] Publish blog posts.
115
+
-[ ] Advertise on Social Media.
116
+
-[ ] Post on public slack and Github Release issue.
-[ ] Create [release tags](https://github.com/opensearch-project/opensearch-build/blob/main/jenkins/release-tag/release-tag.jenkinsfile) for each component (Jenkins job name: release-tag-creation).
92
-
-[ ] Replace refs in [manifests/{{ env.VERSION }}](/opensearch-project/opensearch-build/tree/main/manifests/{{ env.VERSION }}) with tags and remove checks.
93
-
-[ ] If this is a major or minor version release, stop building previous patch version.
94
-
-[ ] Generate distribution release notes reviewed by PM team for opensearch-build repository.
95
-
-[ ] Increment version for Helm Charts [(sample PR)](https://github.com/opensearch-project/helm-charts/pull/246) for the `{{ env.VERSION }}` release.
96
-
-[ ] Increment version for Ansible Charts [(sample PR)](https://github.com/opensearch-project/ansible-playbook/pull/50) for the `{{ env.VERSION }}` release.
97
-
-[ ] Prepare [for next patch release](https://github.com/opensearch-project/opensearch-plugins/blob/main/META.md#increment-a-version-in-every-plugin) by incrementing patch versions for each component.
98
-
-[ ] Update [this template](https://github.com/opensearch-project/opensearch-build/blob/main/.github/ISSUE_TEMPLATE/release_template.md) with any new or missed steps.
99
-
-[ ] Create an issue for a retrospective, solicit feedback, and publish a summary.
-[ ][Decrease the Build Frequency](https://github.com/opensearch-project/opensearch-build/blob/public/RELEASE_PROCESS_OPENSEARCH.md#decrease-the-build-frequency).
0 commit comments