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 phil.steitz@gmail.com
 designates 209.85.160.43 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=jhOOVjGbwsLbUDeQV2+rE+CXoa5JLA/ENAMpbugx+pziW5DwnAjD/ORJEQQqM1EBr8
         IQd+w3PNmpErp/r8bTJMDT78M7NGGqlPTw8o5R+gpZxlRslHG1hLGU6NkxzY/SDvXQQf
         NGjUg3Cpi23eQlUv+riDuVUFT7PQLNjX+N89M=
Message-ID: <4DEECAC4.5030209@gmail.com>
Date: Tue, 07 Jun 2011 18:05:08 -0700
From: Phil Steitz <phil.steitz@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Commons Developers List <dev@commons.apache.org>
Subject: Re: [DAEMON] Tagging 1.0.6
References: <4DEDF545.6010601@apache.org>
	<BANLkTin_jvLx0R7iYHyspkVpARL+9UapGQ@mail.gmail.com>
	<4DEE61DB.5040904@apache.org>
 <BANLkTimTuRtp6WvHLsjerSR83Uyj45ETNg@mail.gmail.com>
In-Reply-To: <BANLkTimTuRtp6WvHLsjerSR83Uyj45ETNg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 6/7/11 5:40 PM, sebb wrote:
> On 7 June 2011 18:37, Mladen Turk <mturk@apache.org> wrote:
>> On 06/07/2011 12:28 PM, sebb wrote:
>>>> Q: I saw some projects are using svn for releases instead
>>>> copying the artifacts trough the ftp. Are using this as well
>>>> or the [1] is still valid?
>>> AFAIK, that has to be set up through infrastructure first.
>>>
>> Yep that was my understanding as well.
>> Seems like easier then manually copying the files trough scp/ftp
>> so might be something to consider as Commons wide.
> Maybe.
>
> How does it work for release votes?
> Is there a staging area?
> Or is it only used after the vote, at the release stage?

Key thing is we need to be sure that what we vote on are the bits
that get deployed.  How exactly can that work if the RM is
committing something and a commit hook pushes it automatically to dist?

>>> [1] does not cover components using Nexus, which includes Daemon.
>>> In which case "mvn deploy" will copy the artifacts (Maven and
>>> otherwise) to the staging repo.
>>> See [2] and [3] for further info.
>>>
>> I had problems earlier when trying to deploy the artifacts to maven.
> I think that was before Nexus; also Commons Parent has been improved since then.
>
>> Will you (or someone else) help me with that once we have
>> the 1.0.6 voted?
> I'm happy to help, but the deployment needs to be done before the
> vote, as the Maven artifacts need to be included in the vote.

We need to VOTE on the maven artifacts, but technically this could
be in a separate vote after the release to dist.

Phil

> I'll try a SNAPSHOT deploy shortly and see if it works OK for the Java code.
>
> Probably best if you sign the Maven code as well, but that should just
> be a question of running the same command as I have.
>
> ---------------------------------------------------------------------
> 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