-
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.2.1 #2481
Comments
Hello OpenSearch community. We have discovered a potential last minute issue and need to perform due diligence on it. The teams are still working on this and we will provide another update by the 31st. Your patience is appreciated. Please refer to https://forum.opensearch.org/t/update-1-3-5-2-2-1-on-hold/10727 for current status. |
We have got a green signal to release 2.2.1 on Sept 01 2022 and we have started prepping for the release. |
Release testing Click to expand and get the latest
|
OpenSearch CommitID(after 2022-07-12) & Release Notes info
|
OpenSearch Dashboards CommitID(after 2022-07-12) & Release Notes info
|
OpenSearch 5997 integ-test result. |
OpenSearch Dashboard 407 integ-test result arm64. without-security arm64
with-security arm64
OpenSearch Dashboard 407 integ-test result x64. without-security x64
with-security x64
|
OpenSearch CommitID(after 2022-08-12) & Release Notes info
OpenSearch Dashboards CommitID(after 2022-08-12) & Release Notes info
|
1.3.5 Native plugin validation to install repository-s3
|
Release 2.2.1 https://opensearch.org/versions/opensearch-2-2-1.html |
Release OpenSearch and OpenSearch Dashboards 2.2.1
I noticed that a manifest was automatically created in manifests/2.2.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
__REPLACE_RELEASE-__
placeholders have actual dates.CI/CD (Feature Freeze) - Aug 19th
<MajorVersion>.<MinorVersion>
early.Code Complete - _Ends Aug 19th
Release testing - _Ends Aug 23th
<MajorVersion>.<MinorVersion>
for the release.### Release - _Ends Aug 25thRelease - _Ends Aug 30th
v2.2.1
in all projects have been resolved.Post Release
2.2.1
release.2.2.1
release.Components
Replace with links to all component tracking issues.
Legend
The text was updated successfully, but these errors were encountered: