-
Notifications
You must be signed in to change notification settings - Fork 273
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.5.0 #2908
Comments
@peterzhuamazon test fix has been merged in opensearch-project/neural-search#106 (opensearch-project/neural-search@e498cba). |
OS Windows integration tests completed. Below are failing components.
|
Passed thanks. |
OSD Windows Integ Test with Security Results:
|
OSD Windows Integ Test without Security Results:
|
X64 DEB integTest: OS Failed:
OSD Failed:
NOSEC_X64_OSD_DEB_1.log
|
ARM64 DEB integTest: OS Failed: Security Analytics NOSEC OSD Failed:
NOSEC_ARM64_OSD_DEB_1.log
|
Integ test results for x64 tarball OSD with security
|
2023/01/18 17:00 New RC OS 6976 & OSD 5367 are ready for your test.New Release Candidate OS 6976 / OSD 5367: (2023/01/18 17:00 PST)OpenSearch - Build 6976 (the failure is due to docker scan not build/assemble)
|
Integ test for OSD tarball on arm64 with security
|
Integ tests for OSD tarball on x64 without security
|
Integ tests of OSD tarball on arm64 without security
|
APT/DEB Runs:
|
Native plugin installation:
|
Maven will be released on maven central soon: Already in release. |
This release is completed at this point. |
Release OpenSearch and OpenSearch Dashboards 2.5.0
I noticed that a manifest was automatically created in manifests/2.5.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
Release Readiness
Release branch readiness - Ends 2023/01/06
2.5.0
version2.5
release branch2.5
branch for the release.CI/CD Freeze - Ends 2023/01/09
2.5
branch and configure the CI to run against2.5
branch.Code Complete - Ends 2023/01/10
Release testing - 2023/01/11 - 2023/01/13
Performance testing validation - 2023/01/12 - 2023/01/13
Release -
2023/01/16 - 2023/01/172023/01/18 - 2023/01/19v2.5.0
in all projects have been resolved.Post Release
2.5.0
release.2.5.0
release.Components
Legend
Issues:
PRs:
The text was updated successfully, but these errors were encountered: