Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates
 209.85.216.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=bx3SV9QEEBE9ODErUrB/t69Ylrv9PUcQyA6rjIsZLsS8XxNBrXS1mID9oB9Wecf6f4
         ZLI2wG7+wOspE5sGOMiLb1cBb3CnjO5RHHVidWEw70CKMx83nIG1P6wYoI/bpTXL/lj4
         sjdYKprA6G49r0Ec3y/xb77F45gkWi8xtwd8o=
MIME-Version: 1.0
In-Reply-To: <4D93EE3B.5050706@gmail.com>
References: <AANLkTinrxEGJx-HhjiZ+cuJ8=_ww931PB19nRFHTrHKv@mail.gmail.com>
	<AANLkTimE24vhPqcw9mZUa7jn=EiMk789d50XqhPUe43e@mail.gmail.com>
	<4D915031.7060802@gmail.com>
	<AANLkTi=cSSzCcdq46KV3hrMPWAr+aZUFwKrJd_JAO+rQ@mail.gmail.com>
	<AANLkTinkLADJ+zKsrSjAmGwg9u4H-+FgnrG+u18GqPMh@mail.gmail.com>
	<4D91F1B5.8050206@gmail.com>
	<AANLkTikorwbckvqG1yGWVWL=T-MnjDG3au1q6e2uY-gq@mail.gmail.com>
	<AANLkTin1Yz=SvxFvZ8ZmF=Zmn71Rpkd_2FNh8SjS5vHm@mail.gmail.com>
	<AANLkTikXZxj-E6_Rysnn7D=MDGzaPex7kdm0Kt6ToD=U@mail.gmail.com>
	<AANLkTi=rV2ZxW3-F9h=qVpehV_yJ8hQzvG5xKYbZOc_D@mail.gmail.com>
	<4D920050.1010501@gmail.com>
	<AANLkTi=dVjSNN1D5ZVr3z0mY5oL3fHsXg5DcoV3Ow+Kf@mail.gmail.com>
	<4D93CD03.8050409@gmail.com>
	<AANLkTinJWz=69J0oCwAOvE8esF0+SLHTzBo2J8pDDUb3@mail.gmail.com>
	<4D93EE3B.5050706@gmail.com>
Date: Thu, 31 Mar 2011 11:33:27 +0100
Message-ID: <AANLkTinhw1Swcc+F6nVF7uu4Tc7VYEmm58BTppN69AmC@mail.gmail.com>
Subject: Re: Release process WAS [VOTE] Release Apache Commons Codec 1.5-RC1
From: sebb <sebbaz@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Cc: Phil Steitz <phil.steitz@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 31 March 2011 04:00, Phil Steitz <phil.steitz@gmail.com> wrote:
> On 3/30/11 6:57 PM, sebb wrote:
>> On 31 March 2011 01:38, Phil Steitz <phil.steitz@gmail.com> wrote:
>>> On 3/30/11 4:22 PM, Jochen Wiedmann wrote:
>>>> On Tue, Mar 29, 2011 at 5:52 PM, Phil Steitz <phil.steitz@gmail.com> w=
rote:
>>>>
>>>>> I disagree with this. =A0The most important artifacts are the
>>>>> zips/tars that go to dist/. =A0These *are* the ASF release. =A0Nexus
>>>>> makes it *harder* IMO to maintain provenance of these artifacts.
>>>> These artifacts are present in Nexus. Pulling them to a temporary
>>>> directory is quite easy with wget.
>>> And then you need to check the hashes and sigs again since you are
>>> now working with downloaded copies of the files that we voted on.
>> Huh?
>>
>> If we create a script to move the files directly from Nexus staging to
>> dist/, surely there's no chance that the cp+rm will somehow mangle the
>> files?
> mv is no problem. =A0wget via http means you get a copy with the
> network between. =A0That is what I was referring to. =A0In that case,
> just like we tell the users, the RM should check hashes and sigs to
> make sure that what actually ends up in dist/ is identical to what
> we voted on.

I was assuming that we would use scp to copy the files between staging
and dist, not wget.

But if wget can cause problems, I've not seen any, and I use wget to
download all the files when voting.
[I have seen problems with Fx downloads; sometimes it silently truncates fi=
les]

>>> Seems much easier and more correct to me to just scp the files to
>>> p.a.o., let people vote on them and *move* exactly those files to
>>> /dist.
>> Which is much what happens with Nexus now, apart from the dist/ move
>> phase which is not yet automated.
>>
> So the nexus staging repo lives on p.a.o? =A0 Does not look like it
> from the IPs, unless there is some aliasing going on. =A0If dist/ is
> itself mirrored on r.a.o, then mv is possible; otherwise the files
> have to be copied across the network, rather than moved. =A0That
> requires a recheck of the hashes.

Huh? How do mirrors survive then?

> Phil
>>>> =A0At which point I can see no
>>>> difference between your proposed solution and this one. And there's
>>>> nothing to do for all the other files that live in Nexus (and must
>>>> live, because Maven is just too important, whether we like it or not).
>>> Sorry, I don't buy that. =A0The tars and zips need to "live" in
>>> /dist. =A0The maven artifacts need to make their way to the maven
>>> mirrors. =A0Having a "staging" repo where we can inspect the maven
>>> bits before they get pushed out is great (though I think our homes
>>> on p.a.o are fine for this). =A0Why can't we just push files directly
>>> there using scp or Ant tasks and then "promote" them to the rsynch
>>> repo using a little script including commands like those in step 3
>>> of http://commons.apache.org/releases/release.html?
>>>>> I also don't see why we *must* rely on proprietary software to
>>>>> manage replication.
>>>> I'm mostly with you on that. I strongly opposed choosing Nexus in
>>>> favour of Archiva for that very reason. But we have Nexus now and I
>>>> wouldn't want to have Commons a swimmer against the rest of the Apache
>>>> tide.
>>> Based on Mark's response, I don't think we are the only ones :)
>>>
>>> Phil
>>>> Jochen
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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
>
>

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