Release OpenSearch and OpenSearch Dashboards 2.13.0
I noticed that a manifest was automatically created in manifests/2.13.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.
| Criteria |
Status |
Description |
Comments |
| Documentation draft PRs are up and in tech review for all component changes |
🟢 |
|
|
| Sanity testing is done for all components |
🟢 |
|
|
Code coverage has not decreased (all new code has tests) |
|
|
We do not have automated checker for this check yet |
| Release notes are ready and available for all components |
🟢 |
|
|
| Roadmap is up-to-date (information is available to create release highlights) |
🟢 |
|
|
| Release ticket is cut, and there's a forum post announcing the start of the window |
🟢 |
|
|
| Any necessary security reviews are complete |
🟢 |
|
|
| Criteria |
Status |
Description |
Comments |
| Performance tests are run, results are posted to the release ticket and there no unexpected regressions |
🟢 |
|
#4433 (comment) |
| No unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days |
🟢 |
|
We do have one medium and high CVE but waiting fix from upstream and yet to reach 60days mark. |
| Documentation has been fully reviewed and signed off by the documentation community. |
🟢 |
|
|
| All integration tests are passing |
🟢 |
|
|
| Release blog is ready |
🟢 |
|
|
OpenSearch-Dashboards 2.13.0 exit criteria status:
| Criteria |
Status |
Description |
Comments |
| Documentation has been fully reviewed and signed off by the documentation community |
🟢 |
|
|
| No unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days |
🟢 |
|
|
| All integration tests are passing |
🟢 |
|
|
| Release blog is ready |
🟢 |
|
|
Release - April 2nd, 2024
Release Checklist
Pre-Release activities
Release activities
Post-Release activities
Components
Replace with links to all component tracking issues.
OpenSearch
OpenSearch Dashboards
Documentation
Legend
| Symbol |
Meaning |
| 🟢 |
On track with overall release |
| 🟡 |
Missed last milestone |
| 🔴 |
Missed multiple milestones |
Release OpenSearch and OpenSearch Dashboards 2.13.0
I noticed that a manifest was automatically created in manifests/2.13.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.13.0 exit criteria status:
OpenSearch-Dashboards 2.13.0 exit criteria status:
Preparation
Campaigns
Release Branch and Version Increment - 19th March, 2024
Feature Freeze - 19th March, 2024
Code Complete - March 19th, 2024
Release Candidate Creation and Testing - March 27th, 2024
Performance testing validation - March 27th, 2024
Pre Release - April 1st, 2024
Release - April 2nd, 2024
Release Checklist.
Release Checklist
Pre-Release activities
Release activities
Completed validation for <>in the logs).Post-Release activities
Post Release
Components
Replace with links to all component tracking issues.
OpenSearch
OpenSearch Dashboards
Documentation
Legend