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

Re: Automating create-a-release-branch

From: Branko Čibej <brane_at_apache.org>
Date: Sat, 16 Dec 2017 12:31:45 +0100

On 15.12.2017 16:31, Julian Foad wrote:
> Julian Foad wrote:
>> I started writing a create-a-release-branch script to automate the
>> part of the procedure documented in
>> http://subversion.apache.org/docs/community-guide/releasing.html#release-branches
>>
>> Attached, in early draft form:
>> tools/dist/create-minor-release-branch.py
> [...]
>> Suggestions invited.
>
> This script is now committed at
>   tools/dist/create-minor-release-branch.py
>
> When it runs 'svn checkout' it adds '-r {2017-12-01}', in order to
> test how it would have worked to create the 1.10 release branch. It
> uses a date there rather than a revision number because multiple
> repositories are involved.
>
> When it wants to runs 'svn commit' and server-side 'svn copy',
> currently it just prints these commands and does not run them.
>
> Both of these facilities for testing are currently hard-coded. It
> needs a way to enable/disable test mode from the command line.

Wouldn't it make sense for this to be part of release.py?

-- Brane
Received on 2017-12-16 12:31:47 CET

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.