Return-Path: 
 <dev-return-108205-apmail-commons-dev-archive=commons.apache.org@commons.apache.org>
Delivered-To: apmail-commons-dev-archive@www.apache.org
Received: (qmail 29224 invoked from network); 22 Mar 2008 18:44:44 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 22 Mar 2008 18:44:44 -0000
Received: (qmail 95333 invoked by uid 500); 22 Mar 2008 18:44:41 -0000
Delivered-To: apmail-commons-dev-archive@commons.apache.org
Received: (qmail 95253 invoked by uid 500); 22 Mar 2008 18:44:41 -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 95244 invoked by uid 99); 22 Mar 2008 18:44:41 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Mar 2008 11:44:41 -0700
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received: from [82.209.166.4] (HELO smtp.bredband2.net) (82.209.166.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Mar 2008 18:43:52 +0000
Received: (qmail 3468 invoked from network); 22 Mar 2008 18:48:39 -0000
Received: from me-4-118-233-83.3.cust.bredband2.com (HELO [192.168.0.3])
 ([83.233.118.4])
          (envelope-sender <dennisl@apache.org>)
          by smtp.bredband2.net (qmail-ldap-1.03) with SMTP
          for <dev@commons.apache.org>; 22 Mar 2008 18:48:39 -0000
Message-ID: <47E5537B.7080009@apache.org>
Date: Sat, 22 Mar 2008 19:44:11 +0100
From: Dennis Lundberg <dennisl@apache.org>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Jakarta Commons Developers List <dev@commons.apache.org>
Subject: Re: [m2][PROPOSAL] Release process
References: <ce1f2ea80803211541x65ab8044mc39cc62472dfea21@mail.gmail.com>
	 <47E442D0.7010106@apache.org>
 <ce1f2ea80803221046s33e8ed38wed58668ae96fc7ee@mail.gmail.com>
In-Reply-To: <ce1f2ea80803221046s33e8ed38wed58668ae96fc7ee@mail.gmail.com>
X-Enigmail-Version: 0.95.6
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Rahul Akolkar wrote:
> On 3/21/08, Dennis Lundberg <dennisl@apache.org> wrote:
>> If I raise my view and just look at the A, B, C and D headings, it
>>  sounds good. But, there shouldn't be two options under B. IMO we should
>>  always use the release plugin. That will give us consistent releases.
>>
> <snip/>
> 
> Or consistently not using it ;-) But in hindsight, I shouldn't have
> put that option in [B] on the table since its serving as a
> distraction. I am OK with removing it.

Right, there should only be one way to do it. If that way involves the 
release-plugin or not will be decided later on.

> 
> -Rahul
> 
> 
>>  Should something be wrong with the release-plugin we'll be consistently
>>  wrong :-) But bugs are meant to be fixed, so that shouldn't be a problem
>>  in the long run.
>>
>>
>>
>>  Rahul Akolkar wrote:
>>  > Based on couple of JIRA comments, it seems there still isn't consensus
>>  > about a release process using m2 at Commons. I'll try to outline the
>>  > process.
>>  >
>>  > <outline>
>>  >
>>  > [A] Release prep
>>  >
>>  > [B] Stage artifacts and site, to some location TBD (entire commands
>>  > below, not abridged etc.):
>>  >
>>  > mvn -Prc release:prepare
>>  > mvn -Prc release:perform
>>  > mvn -Prc site-deploy
>>  >
>>  > Or, if you don't care about the release plugin, after setting final
>>  > versions in [A]:
>>  >
>>  > mvn -Prc deploy
>>  > mvn -Prc site-deploy
>>  >
>>  > [C] Vote
>>  >
>>  > [D] Go live
>>  >
>>  > mvn stage:copy ...
>>  > mvn site-deploy
>>  >
>>  > </outline>
>>  >
>>  > Does this fit your mental model? If not, why not?
>>  >
>>  > Please keep the discussion at a "vision" level. Yes, the outline is
>>  > flawed (all votes don't pass, there are loops etc.) Yes, required pom
>>  > changes are not discussed. But, once process is OK'ed, we will make
>>  > the poms do the right thing :-)
>>  >
>>  > -Rahul
>>  >
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
> 
> 


-- 
Dennis Lundberg

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