search

fluent / fluent-operator

Operate Fluent Bit and Fluentd in the Kubernetes way - Previously known as FluentBit Operator
Apache License 2.0
587 stars 250 forks source link

release 3.2.0 #1343

Closed cw-Guo closed 1 month ago

cw-Guo commented 2 months ago

What this PR does / why we need it:

release 3.2.0

Which issue(s) this PR fixes:

Fixes #

Does this PR introduced a user-facing change?

Additional documentation, usage docs, etc.:

cw-Guo commented 2 months ago

@benjaminhuo i followed the document and also the previous release PRs to create this PR. Reference:

I will create the next PR once you review and merge this one.

Just to confirm, the target branch release-3.2 should be created directly via the UI right?

cw-Guo commented 2 months ago

@benjaminhuo by the way, we may need some automation to automate this process, and also introduce some naming requirements over the PR titles (so that the automation will be easier).

wenchajun commented 1 month ago

I pulled a new branch, https://github.com/fluent/fluent-operator/tree/release-3.2 Are you interested in continuing to finish the rest of the work today? If not, I will finish these remaining jobs.

wenchajun commented 1 month ago

like this https://github.com/fluent/fluent-operator/tree/release-3.1

joshuabaird commented 1 month ago

@cw-Guo @wenchajun @benjaminhuo How do we handle Helm chart versioning? Should the helm chart version track the fluent-operator version? I see the latest helm chart version is v3.1.0 while v3.2.0 of the fluent-operator has been released.

If not, should appVersion be v3.2.0?

benjaminhuo commented 1 month ago

T

@cw-Guo @wenchajun @benjaminhuo How do we handle Helm chart versioning? Should the helm chart version track the fluent-operator version? I see the latest helm chart version is v3.1.0 while v3.2.0 of the fluent-operator has been released.

If not, should appVersion be v3.2.0?

The chart's version and appversion should be updated whenever a release is out. @wenchajun would you help to revise the dev guide ?