Release version 2.0.0 (RC1)

[peterzhuamazon]

This is a component issue for release 2.0.0 (RC1).

Coming from opensearch-project/opensearch-build#1624, please refer to the dates in that post.

Please also follow the following checklist.

How to use this component issue

This Component Issue

This component issue captures the state of the OpenSearch release, on component/plugin level, its assignee is responsible for driving the release of the component. Please contact them or @mention them on this issue for help.

Release Steps

There are several steps to the release process, components that are behind present risk to the release. Component owners resolve tasks on this ticket to communicate with the overall release owner.

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.

You can find all the corresponding dates of each step in the release issue above.

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.0.0 for Min/Core, and 2.0.0.0 for components. Otherwise, keep the version number unchanged for both.

You can find all the date in above issue

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.0.0.

CI/CD

• All code changes for 2.0.0-rc1 are complete.
• Ensure working and passing CI.
• Re(add) this repo to the (if not exist) opensearch-dashboards input manifest.

Pre-Release

• Update your branch in the opensearch-dashboards input manifest.
• Confirm that all changes for 2.0.0-rc1 have been merged.
• Complete integration tests, and update results in the comment, example.
• Find/fix bugs using latest tarball and docker image provided in meta issue.
• Completed release candidate testing build #TBD.
• All intermittent test failures have issues filed.

Release

• Complete documentation.
• Gather, review and publish release notes. add release note for 2.0.0-rc1 #1507
• Verify all issued labeled for this release are closed or labelled for the next release.

Post Release

• Create a release tag.
• Suggest improvements to this template.
• Conduct a retrospect, and publish its results.

[tmarkley]

Retro item: we didn't label issues for RC1 which has caused confusion about what needs to be finished before RC1 vs before 2.0 GA.

[tmarkley]

Retro item: Expectations for removing non-inclusive language (e.g. #1318) by 2.0 was not clear until days before the code freeze date for RC1.

[kavilla]

Retro item: Issue was created with explicit wording for 2.0.0 I have updated to include rc1 since to avoid confusion. For example, All code changes for 2.0.0 are complete. --> All code changes for 2.0.0-rc1 are complete. so that we can say what we know is going for rc1 but will be able to address code changes for 2.0.0 if they are needed.