-
Notifications
You must be signed in to change notification settings - Fork 275
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.4.0 #2649
Comments
New Date:2022/11/08 EOD: New Freeze Date New Release Candidate OS 6476: (2022/11/14 21:00PM PST)#2896 to resolve the performance issues in previous builds. New Release Candidate OS
|
OS 6476 IntegTest (2022/11/15 10:45AM PST)Adding #5250:
Old IntegTest Results (2022/11/14 10:27AM PST)
Below Outdated now (2022/11/09)IntegTest Results: Linux OS integ test results (OUTDATED)
WINDOWS: 240-dashboards-test-4270.txt Failures: windows failed OSD component list (OUTDATED)
|
Performance Test:
|
OpenSearch 2.3.0 vs 2.4.0- Linux (With security) performance stats:
OpenSearch 2.3.0 vs 2.4.0- Linux (Without security) performance stats:
OpenSearch 2.4.0 - Windows vs Linux performance stats:
|
Performance stats:
|
Updated performance stats after code fix ( i.e. After reverting the code that was causing the degradation view this PR)
|
Promote to Production:
|
Verified Docker:
|
Native plugin installation (Validation):
|
Maven: RPM:
WINDOWS:
|
OpenSearch 2.4.0 was released on Nov 15 2022. |
Release OpenSearch and OpenSearch Dashboards 2.4.0
I noticed that a manifest was automatically created in manifests/2.4.0. 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.Campaigns
opensearch.opensearchplugin
addgroupID
field toorg.opensearch.plugin
#2521Release Readiness
Release branch readiness - Ends 2022/10/31
2.4.0
version2.4
release branch2.4
branch for the release.CI/CD Freeze - Ends 2022/11/02
2.4
branch and configure the CI to run against2.4
branch.Code Complete - Ends
2022/11/032022/11/04Release testing - 2022/11/07 - 2022/11/08
2.4
.Performance testing validation - 2022/11/10 - 2022/11/11
Release - **
2022/11/102022/11/15**v2.4.0
in all projects have been resolved.Post Release
2.4.0
release.2.4.0
release.Components
Legend
PRs:
The text was updated successfully, but these errors were encountered: