Roman Kennke wrote:
Am Samstag, den 20.10.2012, 10:03 +0100 schrieb Chris Burdess:
Mario Torre wrote:
No. Updating the ChangeLog is a requirement.
Maybe it's a requirement, but to be honest, is also a very redundant piece of
information that is already in the commit log,
The commit log is not part of the package. People may want to download
the package and see who the contributors were and when; the ChangeLog is
a long established convention for them to do this.
I don't get it. All of the information of the Changelog is also in the
commit history, and if it isn't, it's only a matter of convention to put
it there. Then, when doing a release, it should be a matter of a simple
script to create a ChangeLog in whatever format is required and put it
in the package (I am sure there are existing scripts that accomplish
exactly this out there). *All* of it can be automated, and it makes
branching, merging, etc much easier, especially in the face of
distributed VCSs.
I am agnostic on the issue of how the ChangeLog is maintained, only that
it should be present and maintained. It is not reasonable to expect a
user, having downloaded a GNU package, to have to search around the Web
to find the development project resources, download and install
configuration management systems with which they may not be familiar,
etc etc, simply to see what changes have been made since the last version.
