Johan Corveleyn wrote on Thu, Mar 15, 2018 at 12:00:57 +0100:
> C:\>python tools\dist\release.py write-changelog --include-unlabeled-summaries branches/1.10.x tags/1.10.0-rc1
> * Merge r1825045 from trunk: (r1825285)
> * Merge r1825215 from trunk: (r1825286)
> * Merge r1825306 from trunk: (r1826169)
> * Merge r1825721 from trunk: (r1826064)
> * Merge the r1825024 group from trunk: (r1825287)
> * Merge the r1825736 group from trunk: (r1825795)
>
> Hmmm, write-changelog should be improved to "recurse" into the merged
> revision / group to get those revision's changelog lines instead, or
> to parse it from the subsequent lines of the merge commit itself (as
> it was filled in by svn-role which got the info when processing
> STATUS).
release.py could import backport.parser and sic it on the log message, but
beware of py2/py3 mismatches. (I'm not sure whether release.py works under py3
nor whether backport.py works under py2.)
Received on 2018-03-16 09:50:58 CET