[Workflow] changing CHANGELOG during development

[ahms5]

I would suggest to start updating the CHANGELOG during development. So for each PR the Changelog should be updated in the [Unreleased] section.
this enhances the quality of the changelog, since we write it and review it.
and it makes release easier.

this worklfow is also suggested by https://keepachangelog.com/en/1.0.0/

[mberz]

I'd be in favor. We've already discussed this but did not follow through with it. It would definitely save some work when releasing.

[ahms5]

we could also think about integrating a tool like towncier to help us with this.
Towncrier is a Python tool that automates generating changelogs from small “news fragment” files created alongside each change. This prevents merge conflicts and ensures release notes are written incrementally rather than all at once. When building a release, Towncrier collects the fragments, formats them into a changelog, and clears them out. It is used by pytests and other large packages.

In this way, It would also be possible to add the chnagelogs automatically to the Github release, so it could be build onto pyfar/pyfar#866

[f-brinkmann]

another option would be to have an action that checks if the a pull request changed the history. I guess it would be less overhead but also less fancy

[ahms5]

good Idea, a third option would be to do both :)

[f-brinkmann]

We revisited this in the meeting today and decided to got with the action for now. If we later see that this is not optimal, we could still add towncier.

@hoyer-a takes care of implementation and @pingelit has a code example from gitlab.