-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 version 2.0.0 (RC1) #2245
Comments
#3026 / #3093 is still pending but will likely be merged after RC1 release. Most of the remaining v2.0.0 and backport 2.0 issues have been triaged |
|
Integration tests for core run as a part of our Gradle check workflow, so this has been marked as completed |
Closing this issue as 2.0.0-RC1 has been released. |
This is a component issue for release 2.0.0 (RC1).
Coming from opensearch-project/opensearch-build#1624, please refer to the dates in that post.
Please also follow the following checklist.
How to use this component issue
This Component Issue
This component issue captures the state of the OpenSearch release, on component/plugin level, its assignee is responsible for driving the release of the component. Please contact them or @mention them on this issue for help.
Release Steps
There are several steps to the release process, components that are behind present risk to the release. Component owners resolve tasks on this ticket to communicate with the overall release owner.
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.
You can find all the corresponding dates of each step in the release issue above.
What should I do if my plugin isn't making any changes?
If including changes in this release, increment the version on 2.0 branch to
2.0.0
for Min/Core, and2.0.0.0
for components. Otherwise, keep the version number unchanged for both.You can find all the date in above issue
Preparation
CI/CD
Pre-Release
Release
Post Release
The text was updated successfully, but these errors were encountered: