On Wed, Mar 14, 2018 at 1:07 PM, Johan Corveleyn <jcor...@gmail.com> wrote:
> On Wed, Mar 14, 2018 at 1:06 PM, Johan Corveleyn <jcor...@gmail.com> wrote:
>> On Wed, Mar 14, 2018 at 12:22 PM, Branko Čibej <br...@apache.org> wrote:
>>> On 14.03.2018 08:58, Julian Foad wrote:
>> ...
>>>> If anyone's willing to write a brief list of the changes since RC1, to
>>>> include in the RC2 announcement, that would be an added bonus.
>>>
>>> svn log -v STATUS | grep svn-role. But that wouldn't really work, would
>>> it. :)
>>
>> Maybe try:
>>
>> release.py write-changelog --include-unlabeled-summaries
>> branches/1.10.x tags/1.10.0-rc1
Bah, doesn't yield very good results:
[[[
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)
User-visible changes:
Developer-visible changes:
]]]
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).
--
Johan
