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

Re: 1.7.5 candidates

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Tue, 15 May 2012 21:19:55 +0100

Daniel Shahaf <d.s_at_daniel.shahaf.name> writes:

> Philip Martin wrote on Tue, May 15, 2012 at 21:12:59 +0100:
>>
>> Now that we have enough signatures the next step in the release process
>> is "release.py move-to-dist". Since it requires up to 24 hours for the
>> mirrors to sync I decided to run it now. I now realise that doing this
>> prevents anyone else from signing the release. Perhaps I should put off
>> running move-to-dist as long as possible? Perhaps I should have given
>> notice?
>
> I don't follow. If someone else wants to sign the release, they
> commi to /repos/dist/release/subversion/foo.asc and within 24 hours all
> mirrors will have their signature. It just means we have to wait those
> 24 hours if we want to include their signature in the announcement mail.

Ah! Does that mean people can also sign old releases? Or delete their
signatures from old releases or the release in progress?

-- 
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com
Received on 2012-05-15 22:20:31 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.