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

Re: Improving CHANGES (or at least making it easier to produce)

From: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 30 Aug 2013 12:26:29 +0200

On Fri, Aug 30, 2013 at 11:48:56AM +0200, Johan Corveleyn wrote:
> At my workplace, we have a convention (enforced by pre-commit hook) to
> use a prefix between square brackets ([U] for the user-facing text,
> [S9] for the developer details (our team is called the "system9" team)
> -> which also get extracted to another text file for an overview of
> all the dev-messages of a single release). Here we could use something
> similar to the contribulyzer syntax (for instance "Change: blablabla
> (issue #1234)").

I like this. No need for pre-commit enforcements, of course.

We often don't know in advance which changes will be backported
to a release. I guess we would have to delay updates to CHANGES
until the moment tarballs are rolled. And instead of updating
CHANGES manually we'd simply add or change 'Change:' annotations
in log messages, and the release.py script would update CHANGES
as necessary before tagging a release.
Received on 2013-08-30 12:27:11 CEST

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