[Changelog] Apply Common Community Standard

[kevinmatthes]

I would like to suggest to format the changelog by applying a community standard therefore. This thread is intended to discuss the possible standards as well as their pros and cons.

Applying any form of convention at all is an enhancement in every case since people visiting this repository will then be able to navigate through the changelog more easily.

[kevinmatthes]

Keep a Changelog

[kevinmatthes]

It is well-readable and lightweight when applying. As an example for a repository which already applies this convention, I would like to name sysexits, a Rust crate for application exit codes.

[iainh]

Looking at the format that @mcobzarenco has in the existing Changelog.md, it looks like a format matching Keep a Changelog has been implemented in 0b40784. Does that match what you were thinking or do you think there is more we could do in this document?

[kevinmatthes]

I agree that the basic style how the current CHANGELOG is written is close to the requirements of Keep a Changelog but I would like to suggest to match the category naming and the release date annotation. This would simplify parsing the file, for instance to create a summary for a GitHub release.

[mcobzarenco]

Happy to adopt Keep a Changelog as the house style. As @iainh notes it's pretty much there.

[mcobzarenco]

I created a PR #64