[RELEASE] Release version 2.0.0 #2086
Description
Release OpenSearch and OpenSearch Dashboards 2.0.0
I noticed that a manifest was automatically created in manifests/2.0.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/05/17is 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) - 2022/05/04 to 2022/05/17
- Create Jenkins workflows that run daily snapshot builds for OpenSearch and OpenSearch Dashboards.
- Increment each component version to 2.0.0 and ensure working CI in component repositories.
- Make pull requests to add each component to manifests/2.0.0/opensearch-2.0.0.yml and manifests/2.0.0/opensearch-dashboards-2.0.0.yml with the corresponding checks.
- OpenSearch / OpenSearch-Dashboards core and components teams finalize their features
Campaigns
- [Meta] Plugin remove
rc1qualifiers from2.0branch #2078 - Add backwards compatibility tests for plugins opensearch-plugins#77
- Add auto backport functionality to backport PRs for releases opensearch-plugins#108
- Remove mappings types opensearch-plugins#130
- Remove remaining checked-in binaries (ZIPs, JARs) used in CI/CD #1750
- [2.0] Dashboards Plugin Errors OpenSearch-Dashboards#1206
- Standardize file locations for supporting files opensearch-plugins#127
- Planned Breaking Changes for 2.0 #1780
- [Meta] Deprecate non-inclusive naming OpenSearch#2589
- [Meta] Update integTest gradle scripts to run via remote cluster independently opensearch-plugins#103
Code Complete - 2022/05/04 to 2022/05/17
- Code Complete (
No More Changes commited to 2.0 branch): 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.0.0/opensearch-2.0.0.yml and manifests/2.0.0/opensearch-dashboards-2.0.0.yml have been merged.
- Gather, review and combine the release notes from components repositories.
Release testing - 2022/05/18 to 2022/05/20
- Declare a release candidate build, and provide the instructions with the release candidates for teams on testing (2022/05/18).
- Sanity Testing (2022/05/18 to 2022/05/20): 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 - 2022/05/18 to 2022/05/20
- Performance tests do not show a regression
- Longevity tests do not show any issues
Release - 2022/05/23 to 2022/05/24
- Verify all issues labeled
v2.0.0in all projects have been resolved. - Complete documentation for this release.
- @naarcha 2.0 Release changes documentation-website#601
- @naarcha Fix RPM 2.0 bug documentation-website#612
- Author blog post for this release.
- @krisfreedain 2.0 GA website updates project-website#830
- @jhmcintyre 2.0 blog and FAQ update project-website#839
-
2022/05/23- Publish this release on opensearch.org. -
2022/05/24- Publish a blog post - release is launched!
Post Release
- Create release tags for each component (Jenkins job name: release-tag-creation).
- Replace refs in manifests/2.0.0 with tags and remove checks.
- Generate distribution release notes reviewed by PM team for opensearch-build repository.
- Increment version for Helm Charts (sample PR) for the
2.0.0release. - Increment version for Ansible Charts (sample PR) for the
2.0.0release. - 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.
- Update this template with any new or missed steps.
- Create an issue for a retrospective, solicit feedback, and publish a summary.
Components
Overall status: Post Release 2.0.0 GA has been released, all post release tasks should be worked on and component release tasks closed out.
Next Step: Closing this release task, ETA 2022/05/24
Legend
| Symbol | Meaning |
|---|---|
| 🟢 | On track with overall release |
| 🟡 | Missed last milestone |
| 🔴 | Missed multiple milestones |
Issue tracking (Updated 2022/05/23 14:07 PST)
| State | Total | Bug | Enhancement |
|---|---|---|---|
| Open | 45 | 3 | 11 |
| Closed | 1043 | 117 | 197 |
General Issues:
- Remove 1.3.2 build and enable 2.0.0 GA builds #2087
- [BUG][DISTRIBUTION][2.0.0] PA failed localmaven in snapshot/non-snapshot pipeline for 2.0.0 GA performance-analyzer#209
- [Enhancement] Allow component only build in distribution pipeline #2091
- [Question] How to approach
api/statusapi/reporting/statsroute authentication addition in future releases #2112 - Support multiple values in --component. #2110
- Make rpm build on centos7 and assemble on rockylinux8 to generate digest correctly for FIPS-enabled nodes #2113
- [Distribution] Broken build
could not find java in JAVA_HOME at /opt/java/openjdk-17/bin/java#2120 - [BUG][Distribution][2.0.0] build distribution pipeline stash not found for msg updating causing failure builds #2125
- [Question] Upcoming expiration of our current sub public key (expire on 20220511) #2040
- Enable integTest for 2.0.0 GA builds now #2130
- Add timeout for integTest runs multi-trigger #2133
- Make check for build longer before timeout #2135
- https://github.com/opensearch-project/opensearch-infra/pull/161 (Revert for Perf Test consistency overall)
IntegTest Related Issues
- [BUG][INTEGTEST][2.0.0] IntegTest script of CCR does not support all the params cross-cluster-replication#400
- [BUG][INTEGTEST][2.0.0] Failed on with security integTest for Notifications notifications#460 (integTest fail, but notifications plugin owner again rate this as a expected failure, will PR later but wont block release)
- Make package.json 2.0.0 so that other checks on 2.0.0 GA can pass opensearch-dashboards-functional-test#232
- Add data-test-subj to app analytics tests opensearch-dashboards-functional-test#216