Keep A Changelog Formatted Release Notes

Feature description

This request is related to documentation style.

May I recommend / request that release notes follow the specification outlined on keepachangelog.com? I've been following this methodology for years and really like it. It makes changes extremely visible and "screenable" when looking for fixes particular to particular issues. I suggest creating a template that can be reused with each release to quickly generate the formatted notes.

Problem or use case

I noticed in all recent change logs for more than a year, all changes for the last major release (e.g. 2.0) are also copied in every single minor release. This is excessively verbose. If people want to know the changes in the major release, they can look at the changelog / release notes for that specific version number as I've always done. It's really an extremely minor inconvenience, and even less so if you link to them in the app.

Alternatives or workarounds

None

The issue names no repository files or tests. Start by reading the Keep a Changelog specification and inspecting recent release notes; done means release notes follow the requested format, use a reusable template, and avoid repeating major-release changes in each minor release.