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.
• Cut 2.4 branch

CI/CD

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

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.
• Code Complete: Test within the distribution, ensuring integration, backwards compatibility, and performance tests pass.
• Sanity Testing: Sanity testing and fixing of critical issues found.
• File issues for all intermittent test failures.

Release

• Complete documentation.
• Verify all issued labeled for this release are closed or labelled for the next release.

Post Release

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

[stephen-crawford]

[TRIAGE] @peternied can you head the release and I (@scrawfor99) will assist you? Thank you.

[stephen-crawford]

Copied from dashboards version since it is the same tasks:

Task Update: Contacted PIT asking if there was anything they needed finalized before the freeze; reviewed all tasks; everything is labeled v2.4.0 (already done).

[stephen-crawford]

Update: Went through tagged v2.4.0 issues on the main repo and checked in with anyone who looked like they may brush up with us to see if they need anything. Was just opensearch-project/OpenSearch#4764 and then Windows CI opensearch-project/OpenSearch#1448 that I saw.

[peternied]

@scrawfor99 FYI - I've created branch 2.4. As far as I know we are waiting on resolving the OpenSSL [1] before we can declare feature freeze, should be done after todays Triage meeting.

• [1] OpenSSL engine support is broken #2195

[peternied]

Still waiting on confirmation that the following PR should be backported into 2.x/2.4 coming right up to feature freeze.

• Point in time security changes #2094

[stephen-crawford]

I can't check the boxes but I did the manifest.

[peternied]

Increment the version on the parent branch to the next development iteration.

The autocut increment PR [1] won't work without some manual intervention, @scrawfor99 can you take a look at the previous version update [2] and make a pull request base of create-pull-request/2.5.0-SNAPSHOT onto the 2.x branch?

• [1] [AUTO] Increment version to 2.5.0-SNAPSHOT #2210
• [2] Increment version to 2.4.0.0 #2084

[stephen-crawford]

@RyanL1997 can you check off:

'Increment the version on the parent branch to the next development iteration.'
'Add this repo to the manifest`

[stephen-crawford]

The sanity test checkbox can also be marked. @RyanL1997 and I covered it before and @cwperks covered it more recently. I apologize for not being more able to run it myself but I do not know how to get the configuration settings from the sanity test implemented from scratch. I should be able to after tomorrow though. For now the sanity test is covered still and I believe that @peternied has done a thorough job documenting existing test failures.

We cannot check the integration test box yet as backwards compatibility remains a WIP likewise we have not been able to test against the released version yet since it just came out this evening.

[peternied]

Unchecked Increment the version on the parent branch to the next development iteration. This is blocked on opensearch-project/opensearch-build#2868

[DarshitChanpura]

Unchecked Increment the version on the parent branch to the next development iteration. This is blocked on opensearch-project/opensearch-build#2868

Checked it, as the issue was closed and the version was bumped to 2.5.0 via #2249

[peternied]

@scrawfor99 could you drive the retro and file any issues so we can close this issue out?

[stephen-crawford]

@peternied will do; what does the retrospective entail? I do not see any past issues mentioning it.

Filed an issue with the only suggestion for the template so that box can be checked.

[peternied]

Our release have overall retros, checkout a retro item like this opensearch-project/opensearch-build#880

[stephen-crawford]

Made a security-repo retro as an issue at: #2280 2280