release 3.2.0

[cw-Guo]

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]

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

• release 2.9.0 #1202
• release 2.9.0 #1203

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]

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

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]

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

[joshuabaird]

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

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 ?