Update CHANGELOG #539
I saw this system in some Rust projects and I really liked it.
It puts more emphasis on the actualy CHANGELOG file again..
I think there already was a discussion on what approach to take here (do it via online tool, use file, etc etc.) but I really liked having an actual file in the source code. Some Rust projects even required a change in
CHANGELOG.md in each PR unless a special tag was set. The CHANGELOG file now also has the Markdown suffix now which makes it easier to read it in most online viewers: https://egit.irs.uni-stuttgart.de/fsfw/fsfw/src/branch/mueller/update-changelog/CHANGELOG.md
While it adds some more redundancy to mess up, I like having something within the source code independent of gitea.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?