-
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 1.3.7 #2742
Comments
Existing issues:
|
New builds: 1.3.7 Windows ZIPs: (Note: You can change the build number to latest once we have more builds, right now we fix to 6592 and 4430) |
Not sure if I see the cause of failure here: opensearch-project/OpenSearch-Dashboards#3030. Seems like it built the artifact and still outputted an error. |
@kavilla I post the error msg in that issue, please check. |
KNN temporarity disable the tests to get through the build, will contact @naveenpajjuri and @rishabh6788 on the next step. Thanks |
Release testingWe have release candidates built and ready for testing. OpenSearch docker
OpenSearch-Dashboards docker
Use below artifacts to deploy OpenSearch and OpenSearch Dashboards on different platforms |
Integration tests for Linux are failing for below components:
|
|
|
Signature looks good:
|
Native plugins looks good too:
|
Verified yum installation, everything working as expected.
|
1.3.7 released successfully. |
At times, release date changes towards the end of the release. With release notes are created during pre-release stage, there are chances that release date added in release notes is outdated. With 1.3.7 & 2.4.1 we identify that release date changed but the release date in the release notes wasn't. I propose to add one subsection inside 1.3.7 Release Notes: opensearch-project/OpenSearch#5536 CC @rishabh6788 |
Release OpenSearch and OpenSearch Dashboards 1.3.7
I noticed that a manifest was automatically created in manifests/1.3.7. 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) - 11/29/2022 - 12/06/2022
<MajorVersion>.<MinorVersion>
early.Campaigns
opensearch-project/opensearch-plugins#181
Code Complete - 11/29/2022 - 12/06/2022
Release testing - 12/07/2022 - 12/09/2022
<MajorVersion>.<MinorVersion>
for the release.Performance testing validation - 12/07/2022 - 12/09/2022
Release - 12/12/2022 - 12/13/2022
v1.3.7
in all projects have been resolved.Post Release
1.3.7
release.1.3.7
release.Components
Replace with links to all component tracking issues.
Legend
The text was updated successfully, but these errors were encountered: