-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RELEASE] Release version 2.0.1 #2165
Comments
Integ test for OS arm64
|
integ test for OS x64
|
The integ test for |
Integ tests Issue: |
These are the old release candidates. Please disregard this and look at the new comment below.
|
We will need to re generate the release candidates because of the issue with performance-analyzer-rca. opensearch-project/performance-analyzer-rca#191 |
Release testingWe have new Artifacts built and ready for testing.
|
Native plugins installation validated.
|
Maven published. |
Close this issue as 2.0.1 release is out. |
Release OpenSearch and OpenSearch Dashboards 2.0.1
I noticed that a manifest was automatically created in manifests/2.0.1. Please follow the following checklist to make a release.
How to use this issue
This Release Issue
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 section.
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 release owner completes the tasks in this ticket, whereas component owners resolve tasks on their ticket in their repositories.
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.
Component List
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.
Preparation
Update the Campaigns section to include monitoring campaigns during this release.__REPLACE_RELEASE-__
placeholders have actual dates.Create a release issue in every component repo that links back to this issue, update Components section with these links.(We don't create component release issue for patch release.)Ensure that all release issues created above are assigned to an owner in the component team.CI/CD (Feature Freeze) - _Ends June 8th
Code Complete - _Ends June 9th
Release testing - _Ends June 15th
Release - _Ends June 16th
v2.0.1
in all projects have been resolved.Post Release
2.0.1
release.2.0.1
release.Components
Replace with links to all component tracking issues.
Legend
The text was updated successfully, but these errors were encountered: