-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RELEASE] Release version 2.11.0 #3998
Comments
I am seeing the same error as @dhrubo-os . This seems to be related to observability dashboards plugin. @anirudha Can you look in to this issue? |
Documentation status: RED. Out of 16 issues we are tracking, 5 are Done, 6 are in some state of progress, and 5 are in our backlog. Most issues in our backlog (meaning we have not started them) came in on or after 10/2. We have moved 7 issues to 2.12, and for another one, we are waiting for confirmation as to whether it's in 2.11 or 2.12. For a list of issues we are tracking, see https://github.com/opensearch-project/documentation-website/issues?q=is%3Aissue+label%3Av2.11.0+is%3Aopen. |
@bbarani @dhrubo-os @rishabh6788, Observability has hard dependency on a dashboards feature. Dashboards-Core backport to 2.11 for this commit went in after the initial branch cut. Should be fixed in next RC. |
@ps48 Thank you for the update. |
OpenSearch 8607 / OpenSearch Dashboards 6649 is ready for your test.OpenSearch - Build 8607
Check how to install opensearch and dashboards on different platforms |
OpenSearch 8618 / OpenSearch Dashboards 6651 is ready for your test.OpenSearch - Build 8618
Check how to install opensearch and dashboards on different platforms |
Integration Test status with 3rd RC.All components passing for OpenSearch. See https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test/detail/integ-test/6317/pipeline/104 All Components failing for OpenSearch-Dashboards with Dashboards facing Attached sample dashboards-log file. |
RC#4 OpenSearch 8624 / OpenSearch Dashboards 6654 is ready for your test.OpenSearch - Build 8624
Check how to install opensearch and dashboards on different platforms |
Integration Test status with 4th RC.All components passing for OpenSearch. See https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test/detail/integ-test/6325/pipeline/ Failing Components for OpenSearch-Dashboards: |
Release Notes ReadinessBelow components don't have Release Notes created yet for 2.11.0 OpenSearch:
OpenSearch Dashboards
|
Documentation status: 6 Done, 8 in various stages of doc/tech review, 3 in backlog or in progress. |
RC #5 OpenSearch 8634 / OpenSearch Dashboards 6658 is ready for your test.OpenSearch - Build 8634
Check how to install opensearch and dashboards on different platforms |
RC #6 OpenSearch 8641 / OpenSearch Dashboards 6660 is ready for your test.OpenSearch - Build 8641
Check how to install opensearch and dashboards on different platforms |
Integration Test UpdateAll components integration tests are passing for OpenSearch. See https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test/detail/integ-test/6345/pipeline
For OpenSearch Dashboards below components are failing.
Attached are the log files for teams to take a look and take corrective action. |
Final RC OpenSearch 8649 / OpenSearch Dashboards 6665 is ready for your test.OpenSearch - Build 8649
Check how to install opensearch and dashboards on different platforms |
Integration Test ResultsAll components PASSING for OpenSearch. See https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test/detail/integ-test/6364/pipeline/104 All components PASSING for OpenSearch Dashboards. See https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test-opensearch-dashboards/detail/integ-test-opensearch-dashboards/4283/pipeline/111. OpenSearch Dashboards had a flaky test, passed in second run for OpenSearch Dashboards. See https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test-opensearch-dashboards/detail/integ-test-opensearch-dashboards/4284/pipeline/99/ |
We are 🟢 for 2.11.0 release and it is scheduled to be released on Monday (Oct 16 2023). You can participate in release meeting using this link - https://opensearch.org/events/2023-1018-2-11-release-meetings/ |
Release checklistPre-Release activities
|
We have successfully released |
Release OpenSearch and OpenSearch Dashboards 2.11.0
I noticed that a manifest was automatically created in manifests/2.11.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.
OpenSearch 2.11.0 exit criteria status:
OpenSearch dashboards 2.11.0 exit criteria status:
Performance tests are run, results are posted to the release ticket and there no unexpected regressionsPerformance tests are not executed for OpenSearch DashboardsPerformance tests are not executed for OpenSearch DashboardsPreparation
Campaigns
Release Branch and Version Increment - Ends Oct 04, 2023 - Owner: [Repository Owner, component release manager]
Code Complete - Ends Oct 04, 2023 5PM PST- Owner: [Repository Owner, component release manager, build release manager]
Release Candidate Creation and Testing - Starts Oct 05, 2023 - Owner: [Build release manager]
Performance testing validation - Starts Oct 05, 2023 - Owner: [Repository Owner, component release manager]
Pre Release - TBD - Owner: [Build release manager]
Release - TBD - Owner: [Build release manager]
Release Checklist.
Release Checklist
Pre-Release activities
Release activities
Completed validation for <>
in the logs).Post-Release activities
Post Release
Components
OpenSearch
OpenSearch Dashboards
Legend
The text was updated successfully, but these errors were encountered: