[RELEASE] Release version 1.3.0 #889
Description
Release OpenSearch and OpenSearch Dashboards 1.3.0
I noticed that a manifest was automatically created in manifests/1.3.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.
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
- March 1st is pencils down for feature freeze.
- Update the Campaigns section to include monitoring campaigns during this release.
- Update this issue so all
RELEASE-placeholders have actual dates. - Document any new quality requirements or changes.
- Declare a pencils down date for new features to be merged.
- Finalize scope and feature set and update the Public Roadmap.
- Create a version label in each component repo.
- Create a release issue in every component repo that links back to this issue, update Components section with these links.
- Ensure that all release issues created above are assigned to an owner in the component team.
CI/CD (Feature Freeze) - March 1st
- Create Jenkins workflows that run daily snapshot builds for OpenSearch and OpenSearch Dashboards.
- Increment each component version to 1.3.0 and ensure working CI in component repositories.
- Make pull requests to add each component to manifests/1.3.0/opensearch-1.3.0.yml with the corresponding checks.
- Onboard Dashboards release tests (for each Dashboards plugin owners) onto the functional test repo https://github.com/opensearch-project/opensearch-dashboards-functional-test
Campaigns
- Add backwards compatibility tests for plugins opensearch-plugins#77
- Default CI Java Version to Java 11, run tests on 8, 11, 14 (and attempt 17) opensearch-plugins#64
- Add auto backport functionality to backport PRs for releases opensearch-plugins#108
- Correct copyright notices to reflect Copyright OpenSearch Contributors .github#21
- [Main] onboard Dashboards plugins to functional test repo opensearch-dashboards-functional-test#72
- Remove JCenter Dependencies #1456
Code Complete - Ends March 13th
- Code Complete (March 1st - March 9th): The code corresponding to a specific release is ready and the branch 1.3 is added to the manifest.
- Verify pull requests to add each component to manifests/1.3.0/opensearch-1.3.0.yml has been merged.
Release testing - March 15th - March 16th
- Declare a release candidate build, and publish all test results.
- Sanity Testing (March 15th - March 16th): Sanity testing and fixing of critical issues found by teams. Teams test their component within the distribution, ensuring integration, backwards compatibility, and perf tests pass.
Release - March 17th
- Verify all issued labeled
v1.3.0in all projects have been resolved. - Complete documentation for this release.
- Author blog post for this release.
- Gather, review and publish release notes.
- March 17th- Publish this release on opensearch.org.
- March 17th - Publish blog post - release is launched!
Post Release
- Create release tags for each component.
- Update this template with any new or missed steps.
- Conduct a retrospective, and publish its results.
[Retrospective] Release 1.3.0 #1775
Components
Replace with links to all component tracking issues.
Legend
| Symbol | Meaning |
|---|---|
| 🟢 | On track with overall release |
| 🟡 | Missed last milestone |
| 🔴 | Missed multiple milestones |
Issue:
- [1.3.0][Distribution][BUG] k-NN build failed due to failed to apply plugin class 'org.opensearch.gradle.info.GlobalBuildInfoPlugin' k-NN#306
- [1.3.0][Distribution][BUG] Job Scheduler failed the 1.3.0 build due to failed to apply plugin class 'org.opensearch.gradle.info.GlobalBuildInfoPlugin'. job-scheduler#135
- [BUG] tar: opensearch-1.3.0/jdk/...: implausibly old time stamp 1970-01-01 00:00:00 (JDK 11) in 1.3.0 OpenSearch#2412
- [1.3.0][Distribution][BUG] org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':alerting-core:compileKotlin'. alerting#330
- [1.3.0][integtest] IntegTest failed with security on 1.3.0 anomaly-detection#430
Retro section: