-
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.17.0 #4908
Comments
RC 4 did not meet exit criteria. See RC 5 detailsRC4 details## RC 4 OpenSearch 10288 / OpenSearch Dashboards 7935 is ready for your test. OpenSearch - Build 10288
Check how to install opensearch and dashboards on different platforms Integration Test Results
Thank you |
@msfroh - I was discussing something very similar with @andrross offline. IMO, RC1 generation flow should cut the release branch for core and plugins, automatically serving as the "freeze" trigger. After that we can bump the versions for |
RC5 did not meet the bar for release candidate. See RC6 details belowRC 5 details
RC 5 OpenSearch 10289 / OpenSearch Dashboards 7936 is ready for your test.OpenSearch - Build 10289
Check how to install opensearch and dashboards on different platforms Integration Test Results
Thank you |
RC 6 OpenSearch 10292 / OpenSearch Dashboards 7942 is ready for your test.OpenSearch - Build 10292
Check how to install opensearch and dashboards on different platforms Integration Test Results
Thank you |
Updating the status of 2.17.0 as per today Go/No-Go call:
|
RC 7We have next RC which only contains OpenSearch Dashboards: https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch[…]il/distribution-build-opensearch-dashboards/7944/pipeline We are still seeing the CVE in the scan. Working with the core team to see if is actually an issue or false positive. |
RC 82 components had to patch the software to resolve high CVEs. We will continue to run tests and try to meet the exit criteria. |
All integration tests are passing for all components. Below are the final release candidates for the release. |
We unanimously received a GO for tomorrow’s 2.17.0 release in today's Go/No-Go call. |
Native plugin validation
|
GPG key validation looks good as well:
|
🎉 OpenSearch and OpenSearch-Dashboards 2.17.0 have been release to the public. For feedback and suggestions please see the retrospective issue: #4909 Closing this issue as post release activities are completed as well. |
Release OpenSearch and OpenSearch Dashboards 2.17.0
I noticed that a manifest was automatically created in manifests/2.17.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 (Release Manager) 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. For more information check the the Release Process OpenSearch Guide.
Please refer to the following link for the release version dates: Release Schedule and Maintenance Policy.
Entrance Criteria
Code coverage has not decreased (all new code has tests)OpenSearch 2.17.0 exit criteria status:
OpenSearch-Dashboards 2.17.0 exit criteria status:
Preparation
Campaigns
Release Branch and Version Increment - Ends Sept 03, 2024
Feature Freeze - Ends Sept 03, 2024
Code Complete - Ends
Sept 04, 2024Sept 05, 2024Release Candidate Creation and Testing - Starts Sept 04, 2024 at 4PM PDT
Performance testing validation - Ends Sept 11, 2024
Pre Release - _Ends _Sept 16, 2024
Release - Ends Sept 17, 2024
Release Checklist.
Release Checklist
Pre-Release activities
Release activities
Completed validation for <>
in the logs).Post Release
Components
Replace with links to all component tracking issues.
OpenSearch Dashboards
Legend
The text was updated successfully, but these errors were encountered: