[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: Ben Reser <ben_at_reser.org>
Date: Fri, 30 Aug 2013 15:06:06 -0700

On Fri Aug 30 14:45:24 2013, Branko Čibej wrote:
> Right. The question then is, how do we migrate the 1.8 backport CHANGES
> to trunk? Or do you expect this to be a manual step during the creation
> of the release branch?

I was expecting to do something like this:

svn-role commits the changes with the STATUS entries in the commit
message (as it already does).
add a command to filter out the changes lines since the the previous
minor release to release.py (could also make this list revisions with
changes to files other than just STATUS that are missing the line to
review these)
RM takes that output and then edits it and puts it on trunk.
RM merges trunk changes to branch.

Essentially I want to shift most of the effort in writing the CHANGES
entries for minor releases to the people proposing the backports.
There still needs to be some editing for style and other reasons. But
I'd suspect this will reduce the time spent producing this
significantly since the RM doesn't end up having to try to understand
the details of every change in order to write a CHANGES entry.
Received on 2013-08-31 00:06:41 CEST

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