commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar" <>
Subject Re: [all] RCs and version numbers
Date Tue, 06 Feb 2007 21:00:50 GMT
On 2/6/07, Henri Yandell <> wrote:
> We have two ways:
> 1) Do a mock release called 1.4-rc1. The version number of the source
> is 1.4-rc1, it's tagged 1.4-rc1 etc. It can hang around for ages and
> go into production if a user happens to find it and take it there.
> What we are voting on is the release manager and not the release. I
> believe I'm right in saying that this is becoming frowned on at the
> ASF - but it might just be loud views from a minority - the central
> release faq ( doesn't mention
> it yet.
> 2) Create the release and have it be voted on. The version number of
> the source is 1.4, the svn tag is 1.4-rc1, the 1.4 files are put in a
> 1.4-rc1 directory on your ~foo/ account. It's intended to let us vote
> on the actual release and not to be used in production.
> I'm strongly in favour of 2). It's safer and it makes the release
> easier. The only negatives are:

Same here (for 1 below, we keep RCs low key).


> 1) There's a chance that someone might take a jar from the rc1/
> directory in ~bayard and charge off to use it. So be it - that's there
> risk.
> 2) I don't like leaving svn in a state of having a release version, so
> I roll the version back from 1.4 to 1.4-SNAPSHOT after doing the
> release. An alternative might be to branch 1.4 off for the release and
> have a 1.4-release branch for preparing the release on, but that a)
> still makes me uncomfortable to have a release version in and b) will
> be messy having one of those for every release.
> Hen

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message