Simplify management of Release Notes

[jakobmoellerdev]

What would you like to be added:

• Change all Release Note actions towards generating the Release Notes once and then appending new changes as they come in if possible
• If this is not possible, we should change the Release Notes to be only manually touched up once before the release and take over the release notes from previous candidates where applicable
• Once this is done, we can also get rid of the release notes in the branches themselves because the github release notes can be trusted.

Why is this needed:

Currently the github action for the release drafter (https://github.com/open-component-model/ocm/blob/main/.github/workflows/release-drafter.yaml) is only able to work with the ref that is pointed towards it (i.e. main or the release branch)

This leads to the fact that the automation will overwrite any manual changes made to the release notes. This is impractical since that means that for every release candidate we will have to copy over changes made manually, or create a PR for the release notes.

release-drafter/release-drafter#656

[frewilhelm]

Did you close this issue with the correct PR? This should be #1098 right?

[jakobmoellerdev]

Thanks, no that was by accident

[jakobmoellerdev]

The release notes are now no longer stored in the repo thanks to @hilmarf and we currently generate a draft on every commit to the release branch that is based on the last tag found (for z==0 this is the minor patch notes, for every z>0 it is the patch notes for the next z version). This means that the release notes are automatically updated. Together with the fact that we now have properly labelled and controlled pull requests, we now ensure compliant categories and no longer need to manually append things most of the time. That means that we now dont need to have manual edits anymore in 99% of cases so i consider this done.