You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Release OpenSearch and OpenSearch Dashboards 2.4.0
I noticed that a manifest was automatically created in manifests/2.4.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
Assign this issue to a release owner.
Declare a pencils down date for new features to be merged.
2022/11/04 is pencils down date for code freeze.
Update the Campaigns section to include monitoring campaigns during this release.
Update this issue so all __REPLACE_RELEASE-__ placeholders have actual dates.
Component versions are auto-incremented to 2.4.0 version
Plugins team to ensure working CI in component repositories and merge the version increment PR's.
OpenSearch and OpenSearch-Dashboards core create 2.4 release branch
All components create 2.4 branch for the release.
CI/CD Freeze - Ends 2022/11/02
OpenSearch Engineering Effectiveness team will update the input manifests to point to 2.4 branch and configure the CI to run against 2.4 branch.
Create Jenkins workflows that run daily snapshot builds for OpenSearch and OpenSearch Dashboards.
Code Complete - Ends 2022/11/03 2022/11/04
Code Complete: Make sure that the code for this specific version of the release is ready and the branch corresponding to this release has been added to this release version manifest.
OpenSearch / OpenSearch-Dashboards core and components teams finalize their features
Stop builds for this version of OpenSearch and/or OpenSearch Dashboards in order to avoid accidental commits going in unknowingly. Restart only if necessary else manually run the build workflow and declare new release candidate.
After the initial release candidate creation, send PR to lock input manifest refs of both OS and OSD builds to use HEAD commit ids of the components on branch 2.4.
Sanity Testing (2022/11/07 - 2022/11/08): Sanity testing and fixing of critical issues found by teams. Teams test their components within the distribution, ensuring integration, backwards compatibility, and perf tests pass.
Publish all test results in the comments of this issue.
Release OpenSearch and OpenSearch Dashboards 2.4.0
I noticed that a manifest was automatically created in manifests/2.4.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
opensearch.opensearchpluginaddgroupIDfield toorg.opensearch.plugin#2521Release Readiness
Release branch readiness - Ends 2022/10/31
2.4.0version2.4release branch2.4branch for the release.CI/CD Freeze - Ends 2022/11/02
2.4branch and configure the CI to run against2.4branch.Code Complete - Ends
2022/11/032022/11/04Release testing - 2022/11/07 - 2022/11/08
2.4.Performance testing validation - 2022/11/10 - 2022/11/11
Release - **
2022/11/102022/11/15**v2.4.0in all projects have been resolved.Post Release
2.4.0release.2.4.0release.Components
Legend
PRs: