-
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.7.0 #3230
Comments
ml commons dash nosec:
|
The test could have failed because some other dashboards plugin might have added flights sample data and didn’t remove it at the end of their test. So, now this test is looking for an option to install but it was already installed.
|
OBS nosec pass, sec has 2 errors in the run. obs dash nosec
obs dash sec
Error videos: 4_panels.spec.js.mp46_notebooks.spec.js.mp4 |
Observability SignOff : OK 4_panels.spec.js - Bad data on test - test visually worked. Test looking for invalid element. |
2.7.0 is set to release on Tuesday May 2nd. This will allow time to fix issues found in regression tests, as well as implement a fix to address CVE-2022-45688. The releases page has been updated. Thank you for your understanding. Feel free to join OpenSearch public Slack channel for timely updates. |
OpenSearch 7771 / OpenSearch Dashboards 6100 is ready for your test.OpenSearch - Build 7771
Check how to install opensearch and dashboards on different platforms |
Docker images have been promoted and they are looking good.
|
Native plugin install:
|
OpenSearch 2.7.0 has been released. |
Discovered an issue with Job Scheduler Maven publication process and its tracked here |
Missing artifacts for JS have been released: https://aws.oss.sonatype.org/content/repositories/releases/org/opensearch/opensearch-job-scheduler/2.7.0.0/ |
Specifically this issue: |
Release OpenSearch and OpenSearch Dashboards 2.7.0
I noticed that a manifest was automatically created in manifests/2.7.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
__REPLACE_RELEASE-__
placeholders have actual dates.Campaigns
Release Branch - _Ends April 7th
<MajorVersion>.<MinorVersion>
early.<MajorVersion>.<MinorVersion>
branch for the release.Feature Freeze - _Ends April 14th
Code Complete - _Ends April 17th
Release testing - _Ends April 21st
Performance testing validation - _Ends April 21st
Release - _Ends May 2nd
v2.7.0
in all projects have been resolved.Post Release
2.7.0
release.2.7.0
release.Components
Replace with links to all component tracking issues.
Legend
The text was updated successfully, but these errors were encountered: