Return-Path: 
 <commons-dev-return-101603-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org
Received: (qmail 3306 invoked from network); 17 May 2007 15:37:29 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 17 May 2007 15:37:28 -0000
Received: (qmail 69901 invoked by uid 500); 17 May 2007 15:37:25 -0000
Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org
Received: (qmail 69838 invoked by uid 500); 17 May 2007 15:37:25 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 69814 invoked by uid 99); 17 May 2007 15:37:25 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 May 2007 08:37:25 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of wsmoak@gmail.com designates
 209.85.132.249 as permitted sender)
Received: from [209.85.132.249] (HELO an-out-0708.google.com) (209.85.132.249)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 May 2007 08:37:18 -0700
Received: by an-out-0708.google.com with SMTP id c8so157882ana
        for <commons-dev@jakarta.apache.org>;
 Thu, 17 May 2007 08:36:57 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=CcCH/aParo5S+MmZwRXfzu8VqLE2CzWq6GEqRaZ95KWtZ4b7uuF1Gs0YBP2a0FKBb+29XtXljA4HzQeT2dQredbzSnzxIqctwAekOXJlajvR2I7SLyEyfFZCqurz/mFVEh2YKkaLVCdxYbLsX1woUxcB1qL/kJopnOjX+IIpziw=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=UCVQd+UVyHUjJpHIyZ0KH2yWmQgcymK5CTw56J2E2oXn/cEXd2fMXMiUYW1ItsSqefII/yZzfbPXZbSbQe42T2PsVHGE0He2XR4IUYPRaNyINYJHCS+ktnIGOGJQun+/wUHqeqkxUpXtiEJMuJv793KAiwH3xWRWEKPLsoekxl0=
Received: by 10.100.167.7 with SMTP id p7mr389526ane.1179416217543;
        Thu, 17 May 2007 08:36:57 -0700 (PDT)
Received: by 10.100.57.15 with HTTP; Thu, 17 May 2007 08:36:57 -0700 (PDT)
Message-ID: <adba96190705170836g4c575b45je382e6e172e562c0@mail.gmail.com>
Date: Thu, 17 May 2007 08:36:57 -0700
From: "Wendy Smoak" <wsmoak@gmail.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: Re: [all] parent pom repositories
In-Reply-To: <F8B12846-0EA0-4FFB-B04E-BBCFC968041B@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <F8B12846-0EA0-4FFB-B04E-BBCFC968041B@apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

On 5/16/07, Torsten Curdt <tcurdt@apache.org> wrote:

> As we talked about on how to do release on at commons I am wondering
> if these profiles really make sense:
...
>        <id>rc</id>
>        <distributionManagement>
>          <repository>
>            <id>apache.snapshots</id>
>            <name>Apache Development Snapshot Repository</name>
>            <url>${commons.deployment.protocol}://people.apache.org/
> www/people.apache.org/repo/m2-snapshot-repository</url>

Briefly, in no particular order...

Stage each release in a separate repository, such as
people.a.o/builds/commons/[project name]/${version}/m2-staging-repository

There is a utility for promoting staged releases to the rsynced repo.
(Actually for merging one repository into another, including the
metadata.)

The latest release of the gpg plugin will prompt for a passphrase if
one is not supplied.

Signing the release distributions... The gpg plugin will sign them if
you deploy them to the repository (attached assemblies).  There's a
bit of renaming and copying to do that I haven't figured out how to
automate yet.  Then you have to decide if you want the distributions
in the Maven repo.

-- 
Wendy

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