-
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 1.3.6 #2650
Comments
OpenSearch CommitID(after 2022-08-16) & Release Notes info
|
OpenSearch Dashboards CommitID(after 2022-08-16) & Release Notes info
|
Release testing10/04/2022 OpenSearch dockerStart without security
Use TARs to deploy OpenSearch Manuallyarm64 [manifest] [tar] [rpm] [yum]
|
Update 10/05/2022 OpenSearch-Dashboards dockerStart without security OpenSearch Dashboards - Build 4142 arm64 [manifest] [tar][rpm] [yum] |
Integ Test for OS:
x64
|
Native plugins installation validated:
|
Docker validation ✅
OpenSearch docker
OpenSearch dashboard docker
|
Maven artifacts have been released. |
Closing this issue since 1.3.6 is released. https://opensearch.org/versions/opensearch-1-3-6.html |
Release OpenSearch and OpenSearch Dashboards 1.3.6
I noticed that a manifest was automatically created in manifests/1.3.6. 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.- [ ] Create a release issue in every component repo that links back to this issue, update Components section with these linksN/A since we want this would be a lightweight patch release.Ensure that all release issues created above are assigned to an owner in the component team.CI/CD (Feature Freeze) - _Ends Sep 30th
<MajorVersion>.<MinorVersion>
early.Campaigns
REPLACE with OpenSearch wide initiatives to improve quality and consistency.
Code Complete - _Ends Sep 30th
Release testing - _Ends Oct 4th
<MajorVersion>.<MinorVersion>
for the release.Release - _Ends Oct 6th
v1.3.6
in all projects have been resolved.Post Release
1.3.6
release.1.3.6
release.Components
Replace with links to all component tracking issues.
Legend
The text was updated successfully, but these errors were encountered: