-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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.6.0 #6360
Comments
Working on this. |
Starting from |
Note that I've updated #4244 to be tagged for EDIT - @bbarani has updated the roadmap so it now accurate. |
Currently, there are zero open PRs tagged with v2.6.0. I'm currently triaging all issues tagged with v2.6.0 |
Note - I'm planning to cut the |
2.6 branch created - https://github.com/opensearch-project/OpenSearch/tree/2.6 Next step is to bump |
|
Note that we've opted to revert #6414 in the PR - #6431 |
Process to generate release notes:
PR - #6443 |
It can be closed if all Action Items on the component release manager's end is done. |
This is a component issue for 2.6.0.
Coming from opensearch-build__3081__. Please follow the following checklist.
Please refer to the DATES in that post.
How to use this issue
This Component Release Issue
This issue captures the state of the OpenSearch release, on component/plugin level; its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help.
Any release related work can be linked to this issue or added as comments to create visiblity into the release status.
Release Steps
There are several steps to the release process; these steps are completed as the whole component release and components that are behind present risk to the release. The component owner resolves the tasks in this issue and communicate with the overall release owner to make sure each component are moving along as expected.
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. The most current set of dates is on the overall release issue linked at the top of this issue.
The Overall Release Issue
Linked at the top of this issue, the overall release issue captures the state of the entire OpenSearch release including references to this issue, the release owner which is the assignee is responsible for communicating the release status broadly. Please contact them or @mention them on that issue for help.
What should I do if my plugin isn't making any changes?
If including changes in this release, increment the version on
__2.x__
branch to__2.6.0__
for Min/Core, and__2.6.0.0__
for components. Otherwise, keep the version number unchanged for both.Preparation
v2.6.0
.CI/CD
__2.6.0__
are complete.Pre-Release
__2.6__
release branch in the distribution manifest.__2.6.0__
have been merged.Release Testing
Release
Post Release
The text was updated successfully, but these errors were encountered: