Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: AW: New Ivy release
Date: Wed, 18 Mar 2009 06:50:41 +0100
Message-ID: <9EE86F1965E19E499C80DE52AC807B5502A47C89@z011021.bk.fin.local>
Thread-Topic: New Ivy release
Thread-Index: AcmnUWb6Y4hOZuZCSteSRpJqM2w5pQAOwIEg
References: <628822.243.qm@web30804.mail.mud.yahoo.com>
From: <Jan.Materne@rzf.fin-nrw.de>
To: <dev@ant.apache.org>

>it's time to make a new Ivy release.

Cool.


>I volunteer to be release manager,

'handclap'

=20
>but we should discuss the following first:
>
>- what will be the new Ivy version: 2.0.1 or 2.1.0=20
>- what changes will we include in this new release?
>- will we create a release candidate first?


I would anser the 2nd question first. What are these changes?
Are they 'big' or more a bunch of patches? If you answer the 2nd first,
you can
answer these (additional) questions ...

Also for version schema: is there a guideline in Ivy? Maybe a 'reused'
one from=20
Eclipse or OSGi?=20

If you know what changes there are and have a version guideline, it
should be clear
whether 2.0.1 or 2.1.0. Just for PR: a 2.1.0 implies better improvements
and may force
user using that more than a 2.0.1.


A RC version should be done so all could check its content.


>My answers to these questions are:
>- new version: I'd prefer 2.1.0, but I'm ok with 2.0.1 as well
>- what changes: everything that has been committed to trunk
>- release candidate: yes
>
>regards,
>Maarten


Jan

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