search

opensearch-project / opensearch-k8s-operator

OpenSearch Kubernetes Operator
Apache License 2.0
385 stars 202 forks source link

Release v2.6.1 #845

Closed prudhvigodithi closed 3 months ago

prudhvigodithi commented 3 months ago

Release v2.6.1

Coming from the comment by @swoehrl-mw prepare for the release of v2.6.1 by creating a corresponding tag, v2.6.1.

swoehrl-mw commented 3 months ago

@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). Please verify if everything looks alright, and if so, from my view you are good to go to create the tag on the branch and do the release.

prudhvigodithi commented 3 months ago

Thanks @swoehrl-mw, here is the comparison v2.6.0...main and v2.6.0...release-2.6

Excluded for next minor release https://github.com/opensearch-project/opensearch-k8s-operator/pull/838 https://github.com/opensearch-project/opensearch-k8s-operator/pull/808 https://github.com/opensearch-project/opensearch-k8s-operator/pull/788 https://github.com/opensearch-project/opensearch-k8s-operator/pull/770

How about the following @swoehrl-mw looks to me like they can go in this patch release, WDYT? Please let me know. https://github.com/opensearch-project/opensearch-k8s-operator/pull/826 https://github.com/opensearch-project/opensearch-k8s-operator/pull/821 https://github.com/opensearch-project/opensearch-k8s-operator/pull/823 https://github.com/opensearch-project/opensearch-k8s-operator/pull/820 https://github.com/opensearch-project/opensearch-k8s-operator/pull/792

@dbason @swoehrl-mw @jochenkressin @pchmielnik @salyh @getsaurabh02

swoehrl-mw commented 3 months ago

@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.

prudhvigodithi commented 3 months ago

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 main branch ?

swoehrl-mw commented 3 months ago

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 main branch ?

@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.

prudhvigodithi commented 3 months ago

Great, I will move forward with the patch release v2.6.1 from release-2.6 branch. I will raise a PR to prepare for the release.

prudhvigodithi commented 3 months ago

@swoehrl-mw please check this PR https://github.com/opensearch-project/opensearch-k8s-operator/pull/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. @getsaurabh02 @evheniyt

prudhvigodithi commented 3 months ago

Hey Everyone, the release v2.6.1 is completed. A big thank you to all the contributors! :tada:

Release highlights: https://github.com/opensearch-project/opensearch-k8s-operator/releases/tag/v2.6.1

ArtifactHub Download Links: https://artifacthub.io/packages/helm/opensearch-operator/opensearch-operator https://artifacthub.io/packages/helm/opensearch-operator/opensearch-cluster

Jenkins Build Link: https://build.ci.opensearch.org/job/opensearch-operator-release/13/