Release automation

[jpfeuffer]

We should try to automate some more release tasks:

• [ ] Make the param changelog script work on Linux and allow CTDs instead of the full binaries. Makes it much more portable and no full installation of the old version would be required. See also #5833
• [ ] Think about an automatic changelog generator based on pull request labels/strings
• [ ] Make the copyright year script bulletproof. Currently, it is so simple that it needs to be manually inspected to make sure it worked correctly.
• [ ] Try to refactor the version into a VERSION file that is included by CMake and the VersionInfo_test (if we really need this VersionInfo_test, I think it is a bit useless)
• [ ] Have a GitHub actions job, that after a release branch/tag was created, updates the version numbers for a new iteration.
• [ ] Create action that closes the current release milestone and opens a new one (if possible)
• [ ] Perform the release steps in the description of https://abibuilder.informatik.uni-tuebingen.de/jenkins/job/openms/job/ntly/job/conda/ for every release.
• [ ] Since we have new docker containers and moved to GH actions, we should check that those trigger correctly for the next releases and potentially add some stuff for automation there as well.

[jpfeuffer]

Maybe use https://github.com/release-it/release-it

[jpfeuffer]

added conda release to checkboxes

[jpfeuffer]

Some of those tasks are very easy to do. It just means playing around with shell scripts or GH actions.

[tapaswenipathak]

can you update what is done and what is/are remaining?

[jpfeuffer]

Nothing done yet