-
Notifications
You must be signed in to change notification settings - Fork 234
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 v2.7.0 #891
Labels
Comments
prudhvigodithi
added
enhancement
New feature or request
untriaged
Issues that have not yet been triaged
labels
Nov 5, 2024
[Triage] |
prudhvigodithi
added
release
and removed
untriaged
Issues that have not yet been triaged
enhancement
New feature or request
labels
Nov 5, 2024
prudhvigodithi
added a commit
that referenced
this issue
Nov 5, 2024
### Description Prepare for 2.7.0 release ### Issues Resolved Part of #891 ### Check List - [ ] Commits are signed per the DCO using --signoff - [ ] Unittest added for the new/changed functionality and all unit tests are successful - [ ] Customer-visible features documented - [ ] No linter warnings (`make lint`) If CRDs are changed: - [ ] CRD YAMLs updated (`make manifests`) and also copied into the helm chart - [ ] Changes to CRDs documented Please refer to the [PR guidelines](https://github.com/opensearch-project/opensearch-k8s-operator/blob/main/docs/developing.md#submitting-a-pr) before submitting this pull request. By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. For more information on following Developer Certificate of Origin and signing off your commits, please check [here](https://github.com/opensearch-project/OpenSearch/blob/main/CONTRIBUTING.md#developer-certificate-of-origin). Signed-off-by: Prudhvi Godithi <[email protected]>
6 tasks
github-project-automation
bot
moved this from 🆕 New
to ✅ Done
in Engineering Effectiveness Board
Nov 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Coming from #886 (comment) Prepare for the release of v2.7.0 by creating a corresponding tag, v2.7.0.
Change log: v2.6.1...main
The text was updated successfully, but these errors were encountered: