Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: pass (athena.apache.org: domain of paulus.benedictus@gmail.com
 designates 64.233.166.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:mime-version:content-type
         :content-transfer-encoding:content-disposition:x-google-sender-auth;
        b=L0ACkk5keO5s/wWh6GGykN84xcBL8lr/07N7QLQlfcAD4A+AKi0ZCrC+BXhKbdnuQJ
         Mi5zJiydJ4liu0EoeFSxikLnvDJhJy2ctAbAemScY5aLU6R6sQ8OIATqLC8YaKLDrXLv
         Zeryvvfw7qj62fvJemoke/o2xGnSmaeKSn4ig=
Message-ID: <b9e663070808271651w4a785071k64fcc9348deca712@mail.gmail.com>
Date: Wed, 27 Aug 2008 18:51:39 -0500
From: "Paul Benedict" <pbenedict@apache.org>
Sender: paulus.benedictus@gmail.com
To: "Maven Developers List" <dev@maven.apache.org>
Subject: Some Maven Musings on Versioning
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I just want to throw out some thoughts on versioning.

1) I noticed that the transformation of 2.0.10 -> 2.1 has not (yet)
also brought the renaming of SVN tags. I think this is an eventual
must-do so the future 2.0.10 -- the one designed for critical bug
fixes -- can go forward.

2) There was agreement back in the 2.0.9 release that commits being
applied to both branches and trunk would receive all relevant Fixed
Version numbers in their respective tickets. Please notice that not
many 2.0.10 issues are also marked as 3.0 and 2.1. They really should
be so the whole community can determine which issues are exclusively
for a point release, and which are gracious backports. I don't seem to
have that privilege in JIRA, but I would help if it were given to me,
assuming no one else who is currently able wants to manage those
tickets.

3) The forever lingering 3.0-alpha-1 release (was 2.1-alpha-1) is need
of a release for the sake of moving on. There will never be enough
blockers solved for an alpha release to be prepared for consumption.
It's why it's called an alpha release :-) It's going to work, but not
work well enough. My recommendation is to determine which remaining
issues make the product totally unusable, fix those, and get the first
alpha out the door. The remaining issues can be slated for a very
short 3.0-alpha-2, which would push back the next list to 3.0-alpha-3.

Paul

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