Repository navigation
[RELEASE] Release version 2.12.0 #4115
Copy link
Copy link
Closed
Description
Release OpenSearch and OpenSearch Dashboards 2.12.0
I noticed that a manifest was automatically created in manifests/2.12.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 | 🟢 | #4115 (comment) | |
| Sanity testing is done for all components | 🟢 | ||
| Release notes are ready and available for all components | 🟢 | OS Components, OSD Components |
|
| Roadmap is up-to-date (information is available to create release highlights) | 🟢 | ||
| Release ticket is cut | 🟢 | ||
| Any necessary security reviews are complete | 🟢 |
OpenSearch 2.12.0 exit criteria status:
| Criteria | Status | Description | Comments |
|---|---|---|---|
| Performance tests are run, results are posted to the release ticket and there no unexpected regressions | 🟢 | #4115 (comment) | |
| No unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days | 🟢 | ||
| Documentation has been fully reviewed and signed off by the documentation community. | 🟢 | #4115 (comment) | |
| All integration tests are passing | 🟢 | Manual sign off from comment. | |
| Release blog is ready | 🟢 | #4115 (comment) |
OpenSearch-Dashboards 2.12.0 exit criteria status:
| Criteria | Status | Description | Comments |
|---|---|---|---|
| Documentation has been fully reviewed and signed off by the documentation community | 🟢 | #4115 (comment) | |
| No unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days | 🟢 | ||
| All integration tests are passing | 🟢 | Manual sign off from comment | |
| Release blog is ready | 🟢 | #4115 (comment) |
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
- New Plugin
dashboards-assistantOnboard: [On-boarding]: dashboards-assistant plugin #4322 - New plugin
opensearch-skillsonboard: [On-boarding]: Onboarding skills to build repo #4378 - New Plugin
opensearch-flow-frameworkOnboard: [On-boarding]: opensearch-flow-framework plugin #4209 - Component Release Issue.
- Blocked Issues and PR's:
- Release Campaigns.
Release Branch and Version Increment - End of February 4th, 2024
- Core Release Branch.
- Core Version Increment.
- Components Release Branch.
- Components Version Increment.
Feature Freeze - End of February 5th, 2024
- OpenSearch / OpenSearch-Dashboards core and components teams finalize their features.
Code Complete - End of February 5th, 2024
- Mark this as done once the Code Complete is reviewed.
- Create/Verify pull requests to add each component to relase input manifests/2.12.0/opensearch-2.12.0.yml and manifests/2.12.0/opensearch-dashboards-2.12.0.yml.
Release Candidate Creation and Testing - First RC Generated (release window opens) on February 6th, 2024
- Generate Release Candidate.
- 1st RC generation details started on 02/06/2024: [RELEASE] Release version 2.12.0 #4115 (comment).
- 2nd RC generation details started on 02/07/2024: [RELEASE] Release version 2.12.0 #4115 (comment).
- RC Paused on 02/08/2024 [RELEASE] Release version 2.12.0 #4115 (comment).
- 3rd RC generation details started on 02/09/2024 [RELEASE] Release version 2.12.0 #4115 (comment).
- 4th RC generation details started on 02/12/2024 [RELEASE] Release version 2.12.0 #4115 (comment).
- 5th RC generation details started on 02/12/2024 [RELEASE] Release version 2.12.0 #4115 (comment).
- 6th RC generation details started on 02/13/2024 [RELEASE] Release version 2.12.0 #4115 (comment).
- 7th RC generation details started on 02/14/2024 [RELEASE] Release version 2.12.0 #4115 (comment).
- 8th RC generation details started on 02/15/2024 [RELEASE] Release version 2.12.0 #4115 (comment)
- 9th RC generation details started on 02/16/2024 [RELEASE] Release version 2.12.0 #4115 (comment)
- 10th RC generation details started on 02/19/2024 [RELEASE] Release version 2.12.0 #4115 (comment) 🟢 - Integ Test TAR.
- Integ Test RPM.
- Docker Build and Scan.
- Backwards Compatibility Tests.
- Windows Integration Test.
- Broadcast and Communication.
- Release Candidate Lock [Release 2.12.0] RC commit lock #4460.
Performance testing validation - End of February 17th, 2024
- Post the benchmark-tests
- Longevity tests do not show any issues.
Pre Release - End of February 20th, 2024
Release - February 20th, 2024
- Maven Promotion.
- Docker Promotion.
- Release Validation.
- Collaboration with the Project Management Team.
Release Checklist.
Release Checklist
Pre-Release activities
- Promote Repos.
- Promote Artifacts.
-
- Linux Debian
-
- Linux RPM
-
- Linux TAR
- Consolidated Release Notes.
[Release 2.9.0] Consolidated release notes #3803
Release activities
- Docker Promotion: https://build.ci.opensearch.org/job/docker-promotion/62/console
- 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: https://build.ci.opensearch.org/job/publish-to-maven/28/
- Publish blog posts.
- Advertise on Social Media.
- Post on public slack and Github Release issue.
Post-Release activities
- Release Tags.
https://build.ci.opensearch.org/job/distribution-release-tag-creation/98/console
https://build.ci.opensearch.org/job/distribution-release-tag-creation/99/console
https://build.ci.opensearch.org/job/distribution-release-tag-creation/100/ - Input Manifest Update: https://github.com/opensearch-project/opensearch-build/pull/4467/files
- Decrease the Build Frequency.
- OpenSearch Build Release notes: https://github.com/opensearch-project/opensearch-build/releases/tag/2.12.0
- Retrospective Issue: [Retrospective] Release 2.12.0 #4454
- Helm and Ansible Playbook release.
[Release 2.12.0] app update and security admin change helm-charts#518
[Release 2.12.0] Update the OS and OSD version to 2.12.0 ansible-playbook#153 - Upcoming Release Preparation: This process is automated as the version increment PR's, release issues are created by automated workflows.
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
OpenSearch
OpenSearch Dashboards
Documentation
| Component | Issues tagged with 2.12.0 |
|---|---|
| https://github.com/opensearch-project/documentation-website/ |
Legend
| Symbol | Meaning |
|---|---|
| 🟢 | On track with overall release |
| 🟡 | Missed last milestone |
| 🔴 | Missed multiple milestones |
Reactions are currently unavailable
Metadata
Metadata
Assignees
Type
Projects
- StatusShow more project fieldsDone
Activity
derek-ho commentedon Dec 21, 2023
This should also be added to exit criteria for 2.12.0 release: opensearch-project/security#3624
prudhvigodithi commentedon Jan 3, 2024
2.12.0release dates will be finalized based on the discussion part of the issue #4290.Thank you
prudhvigodithi commentedon Jan 5, 2024
The release calendar is updated and
2.12.0is scheduled to February 20th, 2024, I have updated the issue details with all the release timelines. The First RC will be Generated on February 6th, 2024.Thanks
zelinh commentedon Jan 17, 2024
Noticed a build issue with
flow-frameworkplugin for 2.12.0.opensearch-project/flow-framework#410
cc: @prudhvigodithi
peterzhuamazon commentedon Feb 6, 2024
All IntegTest issues and PRs here:
hdhalter commentedon Feb 6, 2024
Documentation update: We are RED for the RC with 2 PRs outstanding:
Update 2/14: Documentation is GREEN. We have PRs up for all 2.12 features: 44 PRs completed and merged; 4 PRs in final review stages.
prudhvigodithi commentedon Feb 7, 2024
1st RC build and results - 02/06/2024
🔴 OpenSearch: https://build.ci.opensearch.org/job/distribution-build-opensearch/9353/console
OpenSearch Failed components: performance-analyzer, skills
🟢 OpenSearch Dashboard: https://build.ci.opensearch.org/job/distribution-build-opensearch-dashboards/7242/console
Components Integ test failures: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aopensearch-project+label%3Av2.12.0+label%3Aautocut+%5BAUTOCUT%5D+integration+in%3Atitle+
90 remaining items
AWSHurneyt commentedon Feb 20, 2024
Providing manual sign off for
alertingDashboards.The tests pass with security in this run from earlier today - https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test-opensearch-dashboards/detail/integ-test-opensearch-dashboards/5633/pipeline/117#step-638-log-678
And the tests pass without security in this run from 3 days ago - https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test-opensearch-dashboards/detail/integ-test-opensearch-dashboards/5621/pipeline/#step-1046-log-162
Since the last new changes merged to the
2.12branch 5 days ago, this suggests the tests are flaky. PR opensearch-project/opensearch-dashboards-functional-test#1115 updated our functional test repo to increase wait times as we noticed it was taking a long time for pages to load, which was causing tests to fail. The tests became much more reliable when executed locally after these changes.kavilla commentedon Feb 20, 2024
For OpenSearch Dashboards,
When looking without-security results. I see the following:
Running locally, the first two spec files succeed every time. With and without security:
The last test failure is due to it trying to open the doc site from the branch 2.12 in the test: https://opensearch.org/docs/2.12/ which doesn't exist yet.
The last one I will associate a PR to ensure that it doesn't kill the test when the doc site tries to open but spins. And I will fix the flakiness of the first two but not seeing anything that worries me there. Manual sign off for me.
ylwu-amzn commentedon Feb 20, 2024
For ml-commons, the test looks flaky as they only failed on ARM64. From the log , seems all tests failed, that's not normal. I guess the integ test cluster has some issue. All failed test throw same error
Connection refused, that seems test cluster not ready or has some issue. Possible reason is the cluster heap size is too small and deploying ML model crashed the cluster.rishabh6788 commentedon Feb 20, 2024
The
stderrlog has the following:@ylwu-amzn
peterzhuamazon commentedon Feb 20, 2024
If this is tar we are testing on CentOS7 and the highest version of glibc is 2.17:
ylwu-amzn commentedon Feb 20, 2024
Thanks Peter, that's the issue. We don't guarantee supporting all hardwares/Operation Systems. Obviously, CentOS7 has some issue with glibc. It's ok for ml-commons release as this is not our SLA to support this. Can we run integ test on other platforms? I manually tested on ARM64 Ubuntu , looks good.
bbarani commentedon Feb 20, 2024
@ylwu-amzn Is this documented somewhere? We still support CentOS 7 at OpenSearch product level so want to make sure that this gap is documented.
ylwu-amzn commentedon Feb 20, 2024
I think no for now. Will add this to our document.
bbarani commentedon Feb 20, 2024
All, OpenSearch 2.12.0 version has been released to public 🎉! This is a power packed release with multiple new features, enhancements and bug fixes as listed on the release notes.
A BIG thank you to everyone who participated in the release !
bbarani commentedon Feb 22, 2024
Please add your comments and feedback to this retrospective issue.
The public retro meeting is scheduled for March 5th 2024 at 9:00AM PDT.
prudhvigodithi commentedon Feb 22, 2024
Thanks everyone, closing this issue.