-
Notifications
You must be signed in to change notification settings - Fork 278
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.11 #3630
Comments
We have release candidates built and ready for testing. Start without security Start with security Start without security Start with security Use below artifacts to deploy OpenSearch and OpenSearch Dashboards on different platforms |
Integ Test ResultsOpenSearch 8029 integ-test result
OpenSearch Dashboards 6320 integ-test result
|
Do we have any updates on the status of this? It looks like all the failures are related or similar. For instance, the SecurityDashboards failure comes after successful cluster checks with an eventual output of
In comparison, alertign dashboards for tar arm x64 comes out with
So the same issue on the surface but nothing obviously specific to one plugin or another. |
Docker-Scan CVEs: OpenSearch, OpenSearch DashBoards |
Docker-Scan CVEs re-run after rebuilding to mitigate CVEs related with AL2 : OpenSearch, OpenSearch DashBoards |
Native plugin installation:
|
ARM64 docker run:
|
Verify signature:
|
Closing this issue as 1.3.11 is released! |
Release OpenSearch and OpenSearch Dashboards 1.3.11
I noticed that a manifest was automatically created in manifests/1.3.11. 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
1.3.11
placeholders have actual dates.Code Complete - Ends June 22nd, 2023
Release testing - Ends June 27th, 2023
Performance testing validation - Ends June 27th, 2023
Release - Ends June 29th, 2023
v1.3.11
in all projects have been resolved.Post Release
1.3.11
release.1.3.11
release.Components
Replace with links to all component tracking issues.
Legend
The text was updated successfully, but these errors were encountered: