Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: domain of ap-cocoon-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: dev@cocoon.apache.org
From: Jorg Heymans <jh@domek.be>
Subject: Re: [2.2] Release?
Date: Wed, 14 Jun 2006 22:39:09 +0200
Lines: 30
Message-ID: <e6ps4g$qpl$1@sea.gmane.org>
References: <448E501B.80701@apache.org> <448F0936.8070304@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
User-Agent: Thunderbird 1.5.0.2 (Macintosh/20060308)
In-Reply-To: <448F0936.8070304@apache.org>
Sender: news <news@sea.gmane.org>


Carsten Ziegeler wrote:

> Finally :) how to we do the actual release? We have to take care of
> legal aspects as well, like adding all licenses of the uses dependencies
> etc.
>

core has a dependency on the licenses block, does that cover your legal
requirements ?


As to how to actually do the release, unsure.  If it was me doing it
next week i would do something like this for the maven part of things:

  1. change the poms manually to reflect the correct version number of
the core (eg 2.2.0M1 or whatever). Also change the version number of
each module itself to be non-snapshot (eg 1.0-SNAPSHOT becomes 1.0).
  2. tag
  3. mvn source:jar javadoc:jar repository:bundle-create for each module
we're releasing, don't forget the module poms
  4. bump the version numbers for all modules, 1.0.0 becomes
1.0.1-SNAPSHOT or 1.1.0-SNAPSHOT etc. Reset the version number of core
back to 2.2.0-SNAPSHOT.
  4. create a jira issue for the jars to be uploaded, described here
http://maven.apache.org/guides/mini/guide-ibiblio-upload.html


HTH
Jorg