Automate parts of the release notes that are "constant" through a minor release

[cahillsf]

Automate parts of the release notes that are "constant" through a minor release by reading from some file to populate the data. For example, the supported kubernetes versions can be maintained in a file on each release branch independently.

Carryover from: #9104

[cahillsf]

/area release

[sbueringer]

/triage accepted

[mcbenjemaa]

I can take this.

[mcbenjemaa]

/assign

[fabriziopandini]

/priority backlog
/kind feature

[kperath]

Since it's been a while unless someone is working on this - I can take it ^^

[kperath]

/assign

[kperath]

Also if we have existing examples of doing this? Any direction is appreciated.

Also I do wonder how useful this is as the given example of a constant section is the "support kubernetes versions" which is a pretty small copy and paste where automating might be overkill. Just a thought to ponder :)

[chandankumar4]

@kperath I believe automating the "constant" part will make the process easier while generating the release notes.
So as mentioned in the issue description we can start from "supported kubernetes versions" which can be maintained in a file on each release branch independently, the release-note-tool will read the version from there while generating.

ping me if you need any help and thanks for picking this up.

[sbueringer]

I'm wondering if this is really worth the effort . This would add the effort of maintaining a file per release branch and add another bit of complexity (sounds like we would then have to run the release note generation on the release branch)

[chandankumar4]

I'm wondering if this is really worth the effort . This would add the effort of maintaining a file per release branch and add another bit of complexity (sounds like we would then have to run the release note generation on the release branch)

Yes, I agree it will add more complexity rather than help in the release process.

[fabriziopandini]

@adilGhaffarDev should we close this one?

[adilGhaffarDev]

yes, let's close this one.

[sbueringer]

/close

[k8s-ci-robot]

@sbueringer: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.