Thomas.Doerfler at embedded-brains.de
Thu Jan 26 09:51:31 UTC 2012
IMHO the question is not whether a given VCS maintains a ChangeLog
internally, the question is more whether the project needs a separate
document containing information about the changes.
My personal opinion is, that a separate, collected ChangLog is quite
useful, even for those users who are not directly working with GIT (e.g.
because they just grab the latest tarball).
The exact format of the ChangeLog is a different question. As long as
GIT is used as the VCS, I tend to let the ChangeLog (at least the
entries of the post-CVS era) be generated automatically. I expect to
avoid problems with the entry format and make sure that the VCS content
and the Changelog content stay in sync.
Am 26.01.2012 08:54, schrieb Sebastian Huber:
> On 01/24/2012 04:24 PM, Ralf Corsepius wrote:
>> It's quite simple: Automated changelogs are nice in small projects (where
>> actually nobody cares about them) but do not meet many larger projects's
>> demands and are a true PITA to use.
> Since the world is great, there are examples for nearly everything. The
> Linux and FreeBSD kernel uses no ChangeLog files at all. What they
> provide are release notes and these are by far more interesting for end
> users than a collection of per file changes.
> Using ChangeLog files and Git is absurd.
Embedded Brains GmbH
Thomas Doerfler Obere Lagerstr. 30
D-82178 Puchheim Germany
email: Thomas.Doerfler at embedded-brains.de
More information about the devel