You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a component issue for 2.17.0.
Coming from opensearch-project/opensearch-build#4908. 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.17.0 for Min/Core, and 2.17.0.0 for components. Otherwise, keep the version number unchanged for both.
Increment the version on the parent branch to the next development iteration.
Gather, review and publish release notes following the rules and back port it to the release branch.git-release-notes may be used to generate release notes from your commit history.
Confirm that all changes for 2.17.0 have been merged.
Add this repo to the manifest for the next developer iteration.
Release Testing
Find/fix bugs using latest tarball and docker image provided in parent release issue and update the release notes if necessary.
Code Complete: Test within the distribution, ensuring integration, backwards compatibility, and performance tests pass.
Sanity Testing: Sanity testing and fixing of critical issues found.
Gentle reminder that we have code cut off date approaching. Sept 04, 2024 4PM PST and we still do not have an assignee for this issue. In order to meet the entrance criteria, please assign an owner to this issue.
Thanks!
Hi @RyanL1997
Just a reminder about release notes that needs to be added to 2.17 branch.
Can you also please check mark all the tasks from the issue description that are complete?
Thanks!
This is a component issue for
2.17.0
.Coming from opensearch-project/opensearch-build#4908. 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 to2.17.0
for Min/Core, and2.17.0.0
for components. Otherwise, keep the version number unchanged for both.Preparation
v2.17.0
.2.17
from the2.x
branch.CI/CD
2.17.0
are complete.Pre-Release
2.17.0
have been merged.Release Testing
Release
Post Release
The text was updated successfully, but these errors were encountered: