-
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.0 #889
Comments
When are the component issues going to be created? |
Once all the items above are done, ie. we don't have a release owner for 1.3 AFAIK or dates, cc: @bbarani |
@zelinh Much of the preparation for release 1.3 hasn't been complete, can this be updated so we can be sure of the dates/deliverables? |
Thanks for reminding. Updated with the dates. |
Issue: opensearch-project/k-NN#306 |
Release testingWe have new Artifacts built and ready for testing.
From Docker Release |
Integration tests for OpenSearch have been run, and here are the results. ARM64
x64
|
UPDATE:
Core OpenSearch Dashboards:
Integ-test (with-security):
Integ-test (with-security):
Note: still working on the flakiness of the tests. Will verify the failures are due to the tests. BWC Tests:ARM64:
x64:
|
Performance Test Results for 1.3
|
On release day (Mar 17, 2022) Maven was released in this URL: https://repo1.maven.org/maven2/org/opensearch/opensearch/1.3.0/ Docker release: https://hub.docker.com/r/opensearchproject/opensearch/tags?page=1&name=1.3.0 |
Release 1.3.0 was completed. Closing this issue. |
The post-release items, such as increment version to 1.3.1, has not been done. I don't see working manifests in https://github.com/opensearch-project/opensearch-build/tree/main/manifests/1.3.1, reopening. |
Closing this since post-release items for 1.3.0 have been done. |
Release OpenSearch and OpenSearch Dashboards 1.3.0
I noticed that a manifest was automatically created in manifests/1.3.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.
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
RELEASE-
placeholders have actual dates.CI/CD (Feature Freeze) - March 1st
Campaigns
Code Complete - Ends March 13th
Release testing - March 15th - March 16th
Release - March 17th
v1.3.0
in all projects have been resolved.Post Release
[Retrospective] Release 1.3.0 #1775
Components
Replace with links to all component tracking issues.
Legend
Issue:
Retro section:
The text was updated successfully, but these errors were encountered: