Repository navigation
[RELEASE] Release version 2.13.0 #4433
Description
Release OpenSearch and OpenSearch Dashboards 2.13.0
I noticed that a manifest was automatically created in manifests/2.13.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 (Release Manager) 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. For more information check the the Release Process OpenSearch Guide.
Please refer to the following link for the release version dates: Release Schedule and Maintenance Policy.
Entrance Criteria
| Criteria | Status | Description | Comments |
|---|---|---|---|
| Documentation draft PRs are up and in tech review for all component changes | 🟢 | ||
| Sanity testing is done for all components | 🟢 | ||
| We do not have automated checker for this check yet | |||
| Release notes are ready and available for all components | 🟢 | ||
| Roadmap is up-to-date (information is available to create release highlights) | 🟢 | ||
| Release ticket is cut, and there's a forum post announcing the start of the window | 🟢 | ||
| Any necessary security reviews are complete | 🟢 |
OpenSearch 2.13.0 exit criteria status:
| Criteria | Status | Description | Comments |
|---|---|---|---|
| Performance tests are run, results are posted to the release ticket and there no unexpected regressions | 🟢 | #4433 (comment) | |
| No unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days | 🟢 | We do have one medium and high CVE but waiting fix from upstream and yet to reach 60days mark. | |
| Documentation has been fully reviewed and signed off by the documentation community. | 🟢 | ||
| All integration tests are passing | 🟢 | ||
| Release blog is ready | 🟢 |
OpenSearch-Dashboards 2.13.0 exit criteria status:
| Criteria | Status | Description | Comments |
|---|---|---|---|
| Documentation has been fully reviewed and signed off by the documentation community | 🟢 | ||
| No unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days | 🟢 | ||
| All integration tests are passing | 🟢 | ||
| Release blog is ready | 🟢 |
Preparation
- Release manager assigned.
- Existence of label in each component repo. For more information check the release-label section.
- Increase the build frequency.
- Release Issue.
Campaigns
Release Branch and Version Increment - 19th March, 2024
- Core Release Branch.
- Core Version Increment.
- Components Release Branch.
- Components Version Increment.
Feature Freeze - 19th March, 2024
- OpenSearch / OpenSearch-Dashboards core and components teams finalize their features.
Code Complete - March 19th, 2024
- Mark this as done once the Code Complete is reviewed.
- Create/Verify pull requests to add each component to relase input manifests/2.13.0/opensearch-2.13.0.yml and manifests/2.13.0/opensearch-dashboards-2.13.0.yml.
Release Candidate Creation and Testing - March 27th, 2024
- Generate Release Candidate.
- Integ Test TAR.
- Integ Test RPM.
- Docker Build and Scan.
- Backwards Compatibility Tests.
- Windows Integration Test.
- Broadcast and Communication.
- Release Candidate Lock.
Performance testing validation - March 27th, 2024
- Post the benchmark-tests
- Longevity tests do not show any issues.
Pre Release - April 1st, 2024
Release - April 2nd, 2024
- Maven Promotion.
- Docker Promotion.
- Release Validation.
- Collaboration with the Project Management Team.
Release Checklist.
Release Checklist
Pre-Release activities
- Promote Repos.
-
- OS
-
- OSD
-
- Promote Artifacts.
-
- Windows
-
- Linux Debian
-
- Linux RPM
-
- Linux TAR
-
- Consolidated Release Notes.
Release activities
- Docker Promotion.
- Release Validation part 1.
-
- OpenSearch and OpenSearch Dashboard Validation.
-
- Validate the native plugin installation.
-
- Merge consolidated release notes PR.
- Website and Documentation Changes.
-
- Merge staging website PR.
-
- Promote the website changes to prod.
-
- Add website alert.
-
- Release Validation part 2.
-
- Validate the artifact download URL's and signatures.
-
- Release Validation part 3.
-
- Trigger the validation build (Search for
Completed validation for <>in the logs).
- Trigger the validation build (Search for
-
- Maven Promotion.
- Publish blog posts.
- Advertise on Social Media.
- Post on public slack and Github Release issue.
Post-Release activities
- Release Tags.
- Input Manifest Update.
- Decrease the Build Frequency.
- OpenSearch Build Release notes.
- Retrospective Issue.
- Helm and Ansible Playbook release.
- Upcoming Release Preparation.
Post Release
- Release Tags.
- Input Manifest Update.
- OpenSearch Build Release notes.
- Decrease the Build Frequency.
- Retrospective Issue.
- Helm and Ansible Playbook release.
- Upcoming Release Preparation.
Components
Replace with links to all component tracking issues.
OpenSearch
OpenSearch Dashboards
Documentation
| Component | Issues tagged with 2.13.0 |
|---|---|
| https://github.com/opensearch-project/documentation-website/ |   |
Legend
| Symbol | Meaning |
|---|---|
| 🟢 | On track with overall release |
| 🟡 | Missed last milestone |
| 🔴 | Missed multiple milestones |
Activity
peterzhuamazon commentedon Mar 15, 2024
Related Issues/PRs:
opensearch-ci-bot commentedon Mar 18, 2024
OpenSearch CommitID(after 2024-02-21) & Release Notes info
opensearch-ci-bot commentedon Mar 18, 2024
OpenSearch Dashboards CommitID(after 2024-02-21) & Release Notes info
hdhalter commentedon Mar 18, 2024
Documentation update: RED for entrance criteria. We have 23 OPEN doc issues with 14 PRs. This means we need to have 9 additional PRs created by tomorrow to be green. 2 issues are DONE.
For the documentation status, see https://github.com/opensearch-project/documentation-website/issues?q=is%3Aissue+is%3Aopen+label%3Av2.13.0.
gaiksaya commentedon Mar 20, 2024
Due to the misses in meeting the entry criteria (release notes, documentation PRs pending) we were not able to generate a viable release candidate even though we have successful builds for both OpenSearch and OpenSearch Dashboards . We have started the testing parallely and the failures should start creating autocut GitHub issues in respective repositories. We will try again tomorrow morning. Please get all the pending release notes and docs PR in by 10AM PST.
You can find more details on this wiki for building, testing and release distributions.
Thanks!
gaiksaya commentedon Mar 21, 2024
Hello everyone,
Due to the misses in meeting the entry criteria (release notes, documentation PRs pending) we were not able to generate a viable release candidate even today even though we have successful builds for both OpenSearch and OpenSearch Dashboards .
Missing release notes components:
asynchronous-searchskillsDocumentation PRs in pending:
https://github.com/opensearch-project/documentation-website/pulls?q=is%3Apr+is%3Aopen+label%3Av2.13.0
Also another critical issue:
Also, performance-analyzer-rca does not have 2.13 branch as it is not a part of manifest automation. Can the maintainers take a look as performance-analyzer plugin uses this as dependency in their build.gradle and checkouts default branch as 2.x
We will try again tomorrow morning. Please get all the pending release notes and docs PR in by 11AM PST.
Thanks!
20 remaining items
gaiksaya commentedon Mar 29, 2024
OpenSearch Dashboards Integ-test results
amsiglan commentedon Mar 29, 2024
Looking at the alertingDashboard test failure video for
RPM X64it looks like the monitor did not finish executing and all alerts couldn't be fetched before we checked for alerts from all monitors. I'm okay with manually signing-off for this test since we have seen it pass reliably in our repo CIs and also on the other platforms it works fine. Will look into making the test more robustps48 commentedon Mar 29, 2024
Giving Manual Sign-off for ganttCharts, observabilityDashboards and reportsDashboards.
For ganttCharts, I see that major failures are
with-securityWe have a PR to make the tenant selection using URL: opensearch-project/opensearch-dashboards-functional-test#1197. For observabilityDashboards and reportsDashboards I see the failures are coming from flaky tests on a couple of distributions.hdhalter commentedon Mar 29, 2024
Documentation is GREEN for the exit criteria. All 38 PRs for 2.13 are merged.
gaiksaya commentedon Mar 29, 2024
RC6 has been finalized as the final RC for 2.13.0 release in today's Go/No-Go call. We will releasing in on 2nd April, 2024.
gaiksaya commentedon Apr 2, 2024
Centralize release workflow run: https://build.ci.opensearch.org/blue/organizations/jenkins/central-release-promotion/detail/central-release-promotion/4/pipeline/714
Validation: https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-validation/detail/distribution-validation/304/pipeline/48/
gaiksaya commentedon Apr 2, 2024
2.13.0 is released to the community now. 🎉
Please use #4602 for feedback/retrospective.
Thank you!
Use global tenant in vis_type_table and other tests (#1210)
Use global tenant in vis_type_table and other tests (#1210)
Use global tenant in vis_type_table and other tests (#1210) (#1218)
Use global tenant in vis_type_table and other tests (opensearch-proje…