commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: Moving to svnpubsub for dist releases
Date Mon, 26 Nov 2012 17:23:41 GMT
On 26 November 2012 17:01, Ralph Goers <ralph.goers@dslextreme.com> wrote:
> Actually, if you use the Release plugin the artifacts will be uploaded to the staging
repository. At least that is what VFS does.  They can be voted on there and then checked into
SVN.  You can easily verify they didn't change because the MD5s go along with them.

But do the MD5s get automatically added to the release vote?
And how can one prove later that the MD5s in the VOTE thread are the
same as the ones in the staging repo?

AFAICT that is no different from uploading to anywhere else, unless I
misunderstand what the release staging repository is.

The point is that uploading to SVN and voting on the URL+revision
automatically provides traceability.
Whereas AFAICT the other methods don't, at least not without
additional work by the RM and all reviewers.

> Ralph
>
> On Nov 26, 2012, at 8:41 AM, sebb wrote:
>
>> On 26 November 2012 11:24, sebb <sebbaz@gmail.com> wrote:
>>> On 26 November 2012 09:53, Emmanuel Bourg <ebourg@apache.org> wrote:
>>>> Le 26/11/2012 01:01, sebb a écrit :
>>>>
>>>>> Hope this all makes sense!
>>>>
>>>> Well, maybe I misunderstood, but committing the RC sites for review into
>>>> a SVN repository seems a bit convoluted to me. A good old upload on
>>>> people.apache.org was perfectly fine.
>>>
>>> AIUI that's what infra want.
>>
>> If the dist/dev URL (plus revision) is used in the vote thread, it's
>> possible to easily trace the files from the ASF mirror back to the
>> actual files used in the vote.
>>
>> This is not nearly so easy if the files are just uploaded to a user
>> directory on minotaur - there's no proof that the the files that were
>> voted on are the ones that were eventually released.
>>
>> At some point the files must be uploaded to SVN; once in SVN they can
>> be moved around very cheaply.
>>
>>>> Emmanuel Bourg
>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message