-
Notifications
You must be signed in to change notification settings - Fork 272
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.3.0 #2447
Comments
Yeah sure I will do that. Thanks a lot. |
OpenSearch CommitID(after 2022-09-06) & Release Notes info
|
OpenSearch Dashboards CommitID(after 2022-09-06) & Release Notes info
|
Added release notes for K-NN, geospatial and customImportMapDashboards |
Performance test runs for this version: |
I compared Side notesBuild numbers used X64Without Security Arm64With Security |
Hi @saratvemulapalli @kotwanikunal @dblock Can you take a look on the above performance test findings? |
@gaiksaya @dreamer-89 trying to look at the runs, is there a human readable format for the results? |
Results attached -
Difference (in %) -
Thanks to Brandon! 🙂 Edit: Results are not anomalous, LGTM! Edit: Updating the results. Sorry for the bad pasting skills. 🤦 |
Thanks @kotwanikunal, looks like our query latency has improved for arm64 without security by quite a bit (>20% lower latency). Do you guys know if you made any expected changes? |
@saratvemulapalli My bad. I swapped the comparisons while pasting. Please have a look again. |
Added release notes for ml-commons. |
Docker scan results: |
Thanks @kotwanikunal. Looks like the results are very similar. We are good to go! |
Hi, |
Getting exception while installing the OpenSearch via tar.
|
@navneet1v Please create an issue with repro steps for the above issue so we can get someone assigned to look into it |
Sure will do that. |
No we have not. We will to do so today. Artifacts are staged after the teams finish the sanity/smoke testing which was yesterday EOD. |
|
Retrospective issue to track any missed steps, improvements: #2620 |
OpenSearch 2.3.0 has been released. 🎊 |
PRs to increment 2.3.0 to 2.3.1 are up for all components. Please review and merge. |
Release OpenSearch and OpenSearch Dashboards 2.3.0
I noticed that a manifest was automatically created in manifests/2.3.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.CI/CD (Feature Freeze) - Ends September 07, 2022
<MajorVersion>.<MinorVersion>
early.Campaigns
Code Complete - Ends September 07, 2022
Release testing - Ends September 12, 2022
<MajorVersion>.<MinorVersion>
for the release.Performance testing validation - Ends September 12, 2022
Release - Ends September 14 2022
v2.3.0
in all projects have been resolved.Post Release
2.3.0
release.2.3.0
release.Components
Replace with links to all component tracking issues.
Legend
The text was updated successfully, but these errors were encountered: