[RELEASE] Release version 2.1.0 #1818

Release OpenSearch and OpenSearch Dashboards 2.1.0

I noticed that a manifest was automatically created in manifests/2.1.0. Please follow the following checklist to make a release.

Preparation

• Assign this issue to a release owner.
• Declare a pencils down date for new features to be merged.
• June 23rd is pencils down date for feature freeze.
• Update the Campaigns section to include monitoring campaigns during this release.
• Update this issue so all __REPLACE_RELEASE-__ placeholders have actual dates.
• Document any new quality requirements or changes.
• Finalize scope and feature set and update the Public Roadmap.
• Create a release issue in every component repo that links back to this issue, update Components section with these links.
• Ensure the label is created in each component repo for this new version, and the next minor release. Create a version label
• Ensure that all release issues created above are assigned to an owner in the component team.

CI/CD (Feature Freeze) - June 29th

• Create Jenkins workflows that run daily snapshot builds for OpenSearch and OpenSearch Dashboards.
• Increment each component version to 2.1.0 and ensure working CI in component repositories.
• Make pull requests to add each component to manifests/2.1.0/opensearch-2.1.0.yml and manifests/2.1.0/opensearch-dashboards-2.1.0.yml with the corresponding checks.
• OpenSearch / OpenSearch-Dashboards core and components teams finalize their features

Campaigns

REPLACE with OpenSearch wide initiatives to improve quality and consistency.

• [Meta] Add automated license header check to all plugins opensearch-plugins#138
• [PROPOSAL] Add flaky test retry  opensearch-plugins#139
• [Meta] Deprecate non-inclusive naming  OpenSearch#2589
  • Deprecate the "Master" nomenclature OpenSearch-Dashboards#1318
  • Change the "Master" nomenclature OpenSearch#472
• [IntegTest] Onboard all plugins into automated integration tests for the distribution #58

Code Complete - Ends June 29th

• 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.
• Verify pull requests to add each component to manifests/2.1.0/opensearch-2.1.0.yml and manifests/2.1.0/opensearch-dashboards-2.1.0.yml have been merged.
• Gather, review and combine the release notes from components repositories.

Release testing - Starts July 1st and Ends July 5th

• Declare a release candidate build, and provide the instructions with the release candidates for teams on testing July 1st.
• Sanity Testing (July 1st - July 5th): 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.

Performance testing validation - Starts July 1st and Ends July 5th

• Performance tests do not show a regression
• Longevity tests do not show any issues

Release - _Ends July 7th

• Verify all issues labeled v2.1.0 in all projects have been resolved.
• Complete documentation for this release.
• Author blog post for this release.
• Publish this release on opensearch.org.
• Publish a blog post - release is launched!

Post Release

• Create release tags for each component.
• Replace refs in manifests/2.1.0 with tags and remove checks.
• Generate distribution release notes reviewed by PM team for opensearch-build repository.
• Prepare for next patch release by incrementing patch versions for each component.
• Lower the frequency of builds for this version of OpenSearch and/or OpenSearch Dashboards. We had stopped builds once the release candidate was ready in order to avoid accidental commits going in.
• Update this template with any new or missed steps.
• Create an issue for a retrospective, solicit feedback, and publish a summary. - Restrospective 2.1.0 release #2257

Components

Replace with links to all component tracking issues.