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 (athena.apache.org: domain of jochen.wiedmann@gmail.com
 designates 209.85.161.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
         :content-type:content-transfer-encoding;
        b=ctEO4fBp1snlUKHLIGGy8fniJ5+v3RMIlaaCp4PO3Tm8VZ4B58GclNmuBTTutczskJ
         7cH7+MpnJODcqJ/lpn/DmxCj2ckmVPsuRumnpH5TGG4869cWY3X+lI6E/Izzlj2VO684
         3ko8b/P0muZJ7oaW2HHoDpVzIKgYMzhetgI9o=
MIME-Version: 1.0
In-Reply-To: <4D93CD03.8050409@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>
Date: Thu, 31 Mar 2011 13:08:20 +0200
Message-ID: <AANLkTi=AceFTSFnRVtX5MYhgyumytjfgJGLCgBa4LJgU@mail.gmail.com>
Subject: Re: Release process WAS [VOTE] Release Apache Commons Codec 1.5-RC1
From: Jochen Wiedmann <jochen.wiedmann@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 31, 2011 at 2:38 AM, Phil Steitz <phil.steitz@gmail.com> wrote:

> 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.
> 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.

You don't get the point of Nexus and the maven-release-plugin, Phil.
The point is that these files (hashes and sigs) are already created,
ready to use and, indeed, will be simply moved to /dist, just as you
are suggesting.


> Sorry, I don't buy that. =C2=A0The tars and zips need to "live" in
> /dist. =C2=A0The maven artifacts need to make their way to the maven
> mirrors. =C2=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). =C2=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?

As I said: Your "little script" would simply be duplicating the
maven-release-plugin. Which is in no way "little".


--=20
I Am What I Am And That's All What I Yam (Popeye)

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