Release Version 2.4.0

[peterzhuamazon]

Release Version 2.4.0

This is a component issue for 2.4.0.
Coming from opensearch-build#2649. Please follow the following checklist.
Please refer to the DATES / CAMPAIGNS in that post.

How to use this issue

This Component Release Issue

This issue captures the state of the OpenSearch release, on component/plugin level; its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help.
Any release related work can be linked to this issue or added as comments to create visiblity into the release status.

Release Steps

There are several steps to the release process; these steps are completed as the whole component release and components that are behind present risk to the release. The component owner resolves the tasks in this issue and communicate with the overall release owner to make sure each component are moving along as expected.

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. The most current set of dates is on the overall release issue linked at the top of this issue.

The Overall Release Issue

Linked at the top of this issue, the overall release issue captures the state of the entire OpenSearch release including references to this issue, the release owner which is the assignee is responsible for communicating the release status broadly. Please contact them or @mention them on that issue for help.

What should I do if my plugin isn't making any changes?

If including changes in this release, increment the version on 2.0 branch to 2.4.0 for Min/Core, and 2.4.0.0 for components. Otherwise, keep the version number unchanged for both.

Preparation

• Assign this issue to a release owner.
• Finalize scope and feature set and update the Public Roadmap.
• All the tasks in this issue have been reviewed by the release owner.
• Create, update, triage and label all features and issues targeted for this release with v2.4.0. @macohen
• Cut 2.4 branch

CI/CD

• All code changes for 2.4.0 are complete. @mingkunm
• Ensure working and passing CI. @mingkunm
• Check that this repo is included in the distribution manifest for 2.4.0 and 3.0.0 #13

Pre-Release

• Update to the 2.4.0 release branch in the distribution manifest.
• Increment the version on the parent branch to the next development iteration.
• Gather, review and publish release notes following the rules and back port it to the release branch.git-release-notes may be used to generate release notes from your commit history.
• Confirm that all changes for 2.4.0 have been merged.
• Add this repo to the manifest for the next developer iteration.

Release Testing

• Find/fix bugs using latest tarball and docker image provided in parent release issue and update the release notes if necessary. @mingkunm
• Code Complete: Test within the distribution, ensuring integration, backwards compatibility, and performance tests pass. @mingkunm
• Sanity Testing: Sanity testing and fixing of critical issues found. @mingkunm
• File issues for all intermittent test failures. @mingkunm

Release

• Complete documentation. @kolchfa-aws
• Verify all issued labeled for this release are closed or labelled for the next release. @macohen

Post Release

• Prepare for an eventual security fix development iteration by incrementing the version on the release branch to the next eventual patch version. @macohen
• Add this repo to the manifest of the next eventual security patch version. @macohen
• Suggest improvements to this template. @macohen
• Conduct a retrospective, and publish its results. @macohen

[macohen]

@peterzhuamazon is there any issue with the CI/CD steps occurring in parallel? I do have a change in my fork to update the manifest, but we're still working on PR #5. which could ensure a working and passing CI.

[peterzhuamazon]

Hi Mark,

The plugin teams control their own CIs which is not the same as the bundle build on Jenkins.
You add your own github actions to test PRs as part of your CIs.
See some other repo just like ml-commons, alerting, job-scheduler for example.

These CIs should run for every PRs, on both linux and windows runners.

Thanks.