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

Re: Generating a daily changelog for /trunk and /branches/1.3.x

From: Tobias Schäfer <tobiasschaefer_at_gmx.de>
Date: 2006-03-12 13:56:51 CET

On Sunday 12 March 2006 13:15, Stefan Küng wrote:
> Kevin Greiner wrote:
> > On 3/12/06, *Stefan Küng* <tortoisesvn@gmail.com
> > <mailto:tortoisesvn@gmail.com>> wrote:
> >
> > I've set it up on my own nightly build machine. I'm just not quite
> > sure if that changelog will be of any real use for the 1.3.x branch: the
> > log messages there aren't really helpful :)

Thanks Stefan, http://mapcar.org/tsvn-snapshots/1.3.x/changelog.html looks

> > At my company, I'm considering installing svn2cl with the output emailed
> > weekly to the entire dev list just to encourage good commit messages.

At my company we are currently generate a Changelog.txt file daily and commit
it to the repository. That increases the revision number daily but that is no
problem at all. Having it in the repository means you always have a faily
current version of Changelog.txt even if you are completely offline.

> The log messages on the branch which I was referring to are not helpful
> in a changelog of the branch only because they're usually like this:
> merge revision xxxx and yyyy from trunk.
> So they only make sense if you have the log from trunk too.

Let us append the actual log message from the revisions we merge to
the usual "Merge revision xxx and yyy from trunk". That might it more
transparent which changes have been merged to the stable branch and will
might increase the number of people downloading the stable nightly.

Something like:
Merge revision xxx and yyy from trunk:
- xxx:<logmessage from revision xxx>
- yyy:<logmessage from revision yyy>

That is hardly more time consuming.


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Mar 12 13:57:44 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.