GNU bug report logs - #13578
A new versioning scheme for automake releases, and a new branching scheme for the Git repository

Previous Next

Full log

View this message in rfc822 format

From: Diego Elio Pettenò <flameeyes <at> flameeyes.eu>
To: Stefano Lattarini <stefano.lattarini <at> gmail.com>,  Automake List <automake <at> gnu.org>, 13578 <at> debbugs.gnu.org
Subject: bug#13578: [IMPORTANT] A new versioning scheme for automake releases, and a new branching scheme for the Git repository
Date: Mon, 11 Feb 2013 16:00:34 +0100

On 11/02/2013 15:54, Stefano Lattarini wrote:
> But what if we want to have multiple betas for, say, Automake 1.14?  Today,
> we can just have 1.13b, 1.13d, 1.13f, ...; how can we do so with the scheme
> you are proposing?

Given that 1.12.0 was "not really final release", and 1.13.0 _and_ .1
were "not really final releases", I would suggest calling the first beta
as 1.14.0 with the big fat warning, then everybody's satisfied (no
missing features, for instance), it rolls as 1.14.4 (say) "really final
release".

This should be more or less equivalent to Apache's versioning, and leads
to decency, I'd say.

-- 
Diego Elio Pettenò — Flameeyes
flameeyes <at> flameeyes.eu — http://blog.flameeyes.eu/

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.