Make the Changelog an actual change log

[atleta]

It seems that you keep overwriting the ChangeLog file/deleting the old content and only keep the latest changes so the only way to actually look at the change log is to dig its commit history. However the very purpose of a change log file would be to show the history of changes.

E.g. the current Changelog file only shows what's new for 3.0.x, but that only works with Django 4.0 so whoever still using Grappelli 2.x won't see anything informative there. And this includes those who plan to upgrade to 3.x (not even 3.0 is included in the Changelog file), which I guess is a larger changeset.

The idea behind a change log file is to be able to find the version I use and then be able to look at all the improvements over time. Please consider merging the individual versions from the git history and keeping a continuous log from this point on.

[sehmaschine]

Good points, but ...

The reason behind this is that I'm not sure how to handle 2 (or more) simultaneous releases which have a different changelogs ... how would you solve this? E.g., if we update 2.15.x ... that cannot go into the changelog of 3.0.x, right?

E.g. the current Changelog file only shows what's new for 3.0.x, but that only works with Django 4.0 so whoever still using Grappelli 2.x won't see anything informative there.

Why should someone who is using Django 3.2 (for example) check the changelog of Grappelli 3.0 (which is not compatible with that version)?