Release OpenSearch and OpenSearch Dashboards 2.7.0
I noticed that a manifest was automatically created in manifests/2.7.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
Campaigns
Release Branch - _Ends April 7th
Feature Freeze - _Ends April 14th
Code Complete - _Ends April 17th
Release testing - _Ends April 21st
Performance testing validation - _Ends April 21st
Release - _Ends May 2nd
Post Release
Components
Replace with links to all component tracking issues.
Legend
| Symbol |
Meaning |
| 🟢 |
On track with overall release |
| 🟡 |
Missed last milestone |
| 🔴 |
Missed multiple milestones |
Release OpenSearch and OpenSearch Dashboards 2.7.0
I noticed that a manifest was automatically created in manifests/2.7.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.Campaigns
Release Branch - _Ends April 7th
<MajorVersion>.<MinorVersion>early.<MajorVersion>.<MinorVersion>branch for the release.Feature Freeze - _Ends April 14th
Code Complete - _Ends April 17th
Release testing - _Ends April 21st
Performance testing validation - _Ends April 21st
Release - _Ends May 2nd
v2.7.0in all projects have been resolved.Post Release
2.7.0release.2.7.0release.Components
Replace with links to all component tracking issues.
Legend