Return-Path: 
 <dev-return-105870-apmail-commons-dev-archive=commons.apache.org@commons.apache.org>
Delivered-To: apmail-commons-dev-archive@www.apache.org
Received: (qmail 45755 invoked from network); 8 Dec 2007 16:01:02 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 8 Dec 2007 16:01:02 -0000
Received: (qmail 89123 invoked by uid 500); 8 Dec 2007 16:00:49 -0000
Delivered-To: apmail-commons-dev-archive@commons.apache.org
Received: (qmail 89061 invoked by uid 500); 8 Dec 2007 16:00:48 -0000
Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@commons.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@commons.apache.org>
List-Post: <mailto:dev@commons.apache.org>
List-Id: <dev.commons.apache.org>
Reply-To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Delivered-To: mailing list dev@commons.apache.org
Received: (qmail 89052 invoked by uid 99); 8 Dec 2007 16:00:48 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Dec 2007 08:00:48 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of rahul.akolkar@gmail.com
 designates 209.85.134.185 as permitted sender)
Received: from [209.85.134.185] (HELO mu-out-0910.google.com) (209.85.134.185)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Dec 2007 16:00:28 +0000
Received: by mu-out-0910.google.com with SMTP id i2so1804287mue
        for <dev@commons.apache.org>; Sat, 08 Dec 2007 08:00:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        bh=JBOl+rgySH6kldn//wyqhH4aBIni76EDMCpN/SDuoUQ=;
        b=uG89j0WewcuhEH4tgstjuR3QiIbxuOfR1B+u1iY/zk8F18E+0t/R1/QKnX3b1bwo7yFQPVapyXsYOwZEW6NOycSwu53NnsBK3PB/9jxeZMb5LQ0NHiJ9vTFv7bKXf8wFUWCiHYJVK69t4khLDkQrYKiauMFcZOvtXSPTBOyhKjI=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=YPIX3tqZ4SzM3BOSRefMT5+AY77zqxjsIFbrrxdnOjsS/+FNlpcZINyP08og4cmk1QSG05yY4TQX3qi1QBOoIhq0v8z+l2ccWed427U4++OezOfjNc5obhyi656MTyJiUAsfRPdAJf4o+rqZjK99+nqCrD6hsShdPLUFIDe6zAI=
Received: by 10.82.158.12 with SMTP id g12mr8425827bue.1197129629214;
        Sat, 08 Dec 2007 08:00:29 -0800 (PST)
Received: by 10.82.140.3 with HTTP; Sat, 8 Dec 2007 08:00:29 -0800 (PST)
Message-ID: <ce1f2ea80712080800s4cb0fa40g516636824bc83985@mail.gmail.com>
Date: Sat, 8 Dec 2007 11:00:29 -0500
From: "Rahul Akolkar" <rahul.akolkar@gmail.com>
To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Subject: Re: [all] m2 release process
In-Reply-To: <55afdc850712071555x5a880abam6cc76b1c4904f2fc@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <55afdc850712071058pef7e8d7tec6f5f4a7467b37@mail.gmail.com>
	 <4759B4AD.2020701@apache.org>
	 <55afdc850712071315h7ca3a1f0kccf0ecf1cdb67448@mail.gmail.com>
	 <4759D815.3020100@apache.org>
	 <55afdc850712071551n1b4b8fb3u74504a7dec71d964@mail.gmail.com>
	 <55afdc850712071555x5a880abam6cc76b1c4904f2fc@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org

On 12/7/07, Niall Pemberton <niall.pemberton@gmail.com> wrote:
<snip/>
>
> OK how about I just upload the artifacts manually - that seems the
> simpest solution.
<snap/>

Sounds good. Do the jars contain LICENSE / NOTICE files? Just saw that
skin-1.0 jars do not!


> Then we can do a commons-parent release removing the
> dummy repository and upgrading to commons-skin 2.
>
<snip/>

We need some discussion on that, since:

 * Haven't seen an answer as to why the dummy repo gets chosen i.e.
given the current setup for commons-skin, whether m2 / deploy-plugin
should (theoretically) choose it in the first place? It would seem
that it wasn't chosen atleast once before (which would be how the 1.0
release was cut), perhaps that is due to differences in plugin
versions used -- which we can lock down, settings.xml minutiae etc.

 * As already pointed out, non-snap versions should never deploy to
rsync repo directly (AIUI, purpose of dummy).

-Rahul

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