- changed status to closed
Please provide regular changelog with released tarballs
It's nice to have webpage, yes. But most (all?) mature projects keep also in-tree changelog (like CHANGES before 5.9, I think).
It should be possible to use a single file (i.e. formatted as rst or in markdown) both for release tarballs and your webpage.
Comments (3)
-
repo owner -
reporter We still maintain the CHANGES file as a work-log
Yes, I see. But my question wasn't answered: why you couldn't provide this file with the release? Is this file can't be checked for misspellings?
not recommended
By who? For example, almost every distribution (e.g. Debian) recommends exactly opposite: provide upstream changelogs (e.g. in /usr/share/doc/package/ dir). FSF recommends ChangeLog as well.
-
repo owner - changed status to resolved
fix Issue
#323: add CHANGES file with a link to the online monit changelog→ <<cset 6c5944f9f6ae>>
- Log in to comment
We still maintain the CHANGES file as a work-log, but it is not distributed. Instead we use https://mmonit.com/monit/changes/ as a curated, grammar checked and more elaborate change-log. If you absolutely need the change-log in raw format (not recommended) you can get it from the repository.