Release v2.6.1 #845
Comments
prudhvigodithi
added
bug
|
@prudhvigodithi I've created a new branch ´release-2.6´ (branched off the v2.6.0 tag) and cherry-picked all the bugfix commits that do not change the CRDs (there were two that fixed problems with the ISMPolicy CRD but I feel better having them in the next normal feature release to be on the safe side). |
github-project-automation
bot
moved this to Backlog
in OpenSearch Engineering Effectiveness
|
Thanks @swoehrl-mw, here is the comparison v2.6.0...main and v2.6.0...release-2.6 Excluded for next minor release How about the following @swoehrl-mw looks to me like they can go in this patch release, WDYT? Please let me know. @dbason @swoehrl-mw @jochenkressin @pchmielnik @salyh @getsaurabh02 |
|
@prudhvigodithi The ones you mention either add new features (which do not belong in a bugfix release) or just change examples/docs and are therefore irrelevant for the branch. |
|
Thanks, what about the case we plan the minor release next time, should we do the same to create a branch and pick the commits? or just release it from the |
@prudhvigodithi This extra branch is only needed for the bugfix releases. For a normal minor/feature release we can just release main as we can include everything. When we one day do a major/breaking release it will need coordination. |
|
Great, I will move forward with the patch release |
|
@swoehrl-mw please check this PR #847 for updating helm charts to prepare for 2.6.1 release. Also Once we have this PR and the proposal issue resolved, we dont have to have helm and operator release coupled. |
### Description Prepare for Release v2.6.1 ### Issues Resolved Part of #845 ### 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]>
|
Hey Everyone, the release v2.6.1 is completed. A big thank you to all the contributors! 🎉 Release highlights: ArtifactHub Download Links: Jenkins Build Link: |
github-project-automation
bot
moved this from Backlog
to Done
in OpenSearch Engineering Effectiveness
Release v2.6.1
Coming from the comment by @swoehrl-mw prepare for the release of
v2.6.1by creating a corresponding tag,v2.6.1.The text was updated successfully, but these errors were encountered: