Release OpenSearch and OpenSearch Dashboards 1.3.16
I noticed that a manifest was automatically created in manifests/1.3.16. 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) |
🔴 |
|
|
| 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 |
🔴 |
|
|
| No unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days |
🔴 |
|
|
| Documentation has been fully reviewed and signed off by the documentation community. |
🔴 |
|
|
| All integration tests are passing |
🔴 |
|
|
| Release blog is ready |
🔴 |
|
|
OpenSearch-Dashboards 1.3.16 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 |
🔴 |
|
|
- [ ] Component Release Issue.
- [ ] Release Campaigns.
- [ ] Core Release Branch.
- [ ] Core Version Increment.
- [ ] Components Release Branch.
- [ ] Components Version Increment.
- [ ] OpenSearch / OpenSearch-Dashboards core and components teams finalize their features.
- [ ] Post the benchmark-tests
- [ ] Longevity tests do not show any issues.
Release - _Ends Apr 23rd
Release Checklist
Pre-Release activities
Release activities
Post-Release activities
Components
| Component |
On track |
Release Notes |
| {COMPONENT_ISSUE_LINK} |
{INDICATOR} |
{STATUS} |
Legend
| Symbol |
Meaning |
| 🟢 |
On track with overall release |
| 🟡 |
Missed last milestone |
| 🔴 |
Missed multiple milestones |
Release OpenSearch and OpenSearch Dashboards 1.3.16
I noticed that a manifest was automatically created in manifests/1.3.16. 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
OpenSearch 1.3.16 exit criteria status:
OpenSearch-Dashboards 1.3.16 exit criteria status:
Preparation
Campaigns- [ ] Component Release Issue.- [ ] Release Campaigns.Release Branch and Version Increment- [ ] Core Release Branch.- [ ] Core Version Increment.- [ ] Components Release Branch.- [ ] Components Version Increment.Feature Freeze- [ ] OpenSearch / OpenSearch-Dashboards core and components teams finalize their features.Code Complete - _Ends Apr 16th
Release Candidate Creation and Testing
Performance testing validation- [ ] Post the benchmark-tests- [ ] Longevity tests do not show any issues.Pre Release - _Ends Apr 22nd
Release - _Ends Apr 23rd
Release Checklist.
Release Checklist
Pre-Release activities
Release activities
Completed validation for <>in the logs).Post-Release activities
Post Release
Components
Legend