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

Teaching 'release.py write-changelog' about merged revisions

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Fri, 5 Oct 2018 14:28:07 +0000

'release.py write-changelog --include-unlabeled-summaries' generates
CHANGES text from 'svn mergeinfo' output on the stable branch. For
merge revisions (such as those committed by svn-role), it currently
picks the first line of the log message, e.g., "Merge r1842260 from

It should instead do two things: one, fetch the log message of the
mentioned revision(s) (r1842260) and pass it through the existing
"Extract CHANGES summary" logic; two, parse the STATUS entry embedded in
the log message, as in the attached example. The script could do either
or these, or even do both and let the RM combine the two versions.

Any volunteers to implement this?



% cd tools/dist
% cat ./foo
r1842626 | danielsh | 2018-10-02 14:42:00 +0000 (Tue, 02 Oct 2018) | 9 lines

Merge r1842260 from trunk:

 * r1842260
   Use the current python executable for launching tests from run_tests.py.
     Attempt to fix 1.10.x tests on the macOS build slave.
     +1: brane, rhuijben, danielsh

% python3
>>> import backport.status
>>> log = open('./foo').read()
>>> backport.status.StatusEntry(log.split('\n\n')[2]).logsummarysummary()
'Use the current python executable for launching tests from run_tests.py.'
Received on 2018-10-05 16:29:46 CEST

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

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