Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4759B4AD.2020701@apache.org>
Date: Fri, 07 Dec 2007 22:01:33 +0100
From: Dennis Lundberg <dennisl@apache.org>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Jakarta Commons Developers List <dev@commons.apache.org>
Subject: Re: [all] m2 release process
References: <55afdc850712071058pef7e8d7tec6f5f4a7467b37@mail.gmail.com>
In-Reply-To: <55afdc850712071058pef7e8d7tec6f5f4a7467b37@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

For logging I followed the current release procedure [1], which worked 
well. Sections 11 and 12 need to be merged somehow. As I'm not familiar 
with releases back in the Jakarta days, I'm not quite sure how to 
though. Other than that, it was obvious what to when the docs talk about 
Maven 1 specifics. But that's probably just me, because I'm used to 
doing releases with Maven 2 over in maven land. So this needs to be 
written down.

For releases support artifacts that reside only in the Central repo 
(parent poms, skin) I have simply done:
- vote based on svn revisions
- mvn release:prepare
- mvn -Prelease release:perform

I'd be happy to help write some more docs for this. We can borrow some 
parts from Maven's own release processes, the old [2] and the new [3]. 
How do we want to structure the docs?

1. One document that includes all releases, whether it's Ant, Maven 1 or 
Maven 2
2. Separate documents depending on which tool is used to do the release
3. Something else...


[1] http://commons.apache.org/releases/release.html
[2] http://maven.apache.org/developers/release/pmc-release-process.html
[3] http://maven.apache.org/developers/release/releasing.html

Niall Pemberton wrote:
> I haven't done an m2 release before - do we have it documented
> anywhere or can someone give me some pointers on what commands and
> options I need to use?
> 
> tia
> 
> Niall
> 
> P.S. This is for commons-skin
> 
> ---------------------------------------------------------------------
> 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