-
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.2 #1882
Comments
@zelinh There are many prepration items that are not complete, is this release still on target? What about the related component issues, are we all are ready for code freeze tomorrow? |
@peternied As I stated above in the preparation part, we don't create component release issue for patch release. We are still targeting the release for next Thursday since we assume there would be lightweight changes (e.g. CVE fix) for patch release. |
@zelinh There are checklist items that are not checked off such as
There are links on this issue like opensearch-project/security-dashboards-plugin#937 should these all be closed? |
Integ-test for OpenSearch arm64
|
integ-test for OpenSearch x64
|
With this backport PR in k-NN repo
|
Release testingWe have new Artifacts built and ready for testing.
|
Native plugin verified
|
Closing the 1.3.2 issue as we have released the distribution. Feel free to re-open this issue if needed. |
Release OpenSearch and OpenSearch Dashboards 1.3.2
I noticed that a manifest was automatically created in manifests/1.3.2. 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 links.(We don't create component issues for lightweight patch release)Ensure that all release issues created above are assigned to an owner in the component team.CI/CD (Feature Freeze) - April 29 2022
Campaigns
REPLACE with OpenSearch wide initiatives to improve quality and consistency.
Code Complete - April 29 2022
Release testing - May 03 - May 04 2022
Release - May 05 2022
v1.3.2
in all projects have been resolved.Post Release
Components
Replace with links to all component tracking issues.
Legend
The text was updated successfully, but these errors were encountered: