[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Automatic ChangeLog generation

From: Ivan-Assen Ivanov <ivanassen_at_gmail.com>
Date: 2004-07-25 07:55:13 CEST

> Perhaps you should use svn log, and generate the ChangeLog when you're
> packaging the software for distribution?

This is the sensible thing to do IMHO.

Users/testers don't care about your revision numbers, and probably
don't care about 80% of your commits. The changelog aimed at them
should contain large-scale items, like "implemented feature X" or
"fixed several network-related bugs on Win32", and viewed from the
perspective of a delta between two subsequent "builds", or "point
releases". So the proper place to generate a changelog is the

In our buildscript, we insert the diff/log between the current
revision and the revision of the previous build, in the beginning of
the old changelog; then the person responsible for the build process
must manually edit it, review the changes and abridge/translate them
into something the testers would understand - basically, what old bugs
we think are fixed, and what new features can already be tested.

It helps if you have a convention in place to denote with a special
message log syntax bugfix commits (fixes bug #340) and a standartized
list of features, e.g. in the design document.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jul 25 07:55:30 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.