Re: [RFC] 3.1 branching

On Thu, 2008-09-25 at 05:00 +1200, Amos Jeffries wrote:

> Just brain dumping at 4am, but, how about this:
>
> stuff goes into HEAD (3-)
> ... after a period we branch (3.1) with features from HEAD
> ... fix all known bugs and release 3.1.0-rc1
> ... if confirmed stable gets officially released as 3.1.1
> ... any critical bug found, or large accumulation of minor ones causes
> 3.1.2 etc
> ... work continues on HEAD for next branching point of (3.2).

This is much better than the current scheme and is similar to what
Kinkie proposed. The three schemes differ in when pre-stable releases of
a branch are made and how they are numbered:

Alex (release development versions early and until no bugs left; keep
metadata elsewhere):
    3.1.0, 3.1.1, 3.1.2, ... 3.1.27, 3.1.28, ...

Kinkie (release development versions early and until no bugs left;
x.y.0.z means "devel" or "beta"; x.y.1 and later are stable):
    3.1.0.0, 3.1.0.1, 3.1.0.2, ... 3.1.1, 3.1.2, ...

Amos: (use BZR snapshots for development, release first numbered version
when all bugs are fixed; x.y.0-rcZ means "release candidate"):
    ... 3.1.0-rc1, 3.1.0-rc2, 3.1.0-rc3, ... 3.1.1, 3.1.2, ...

Is this summary correct?

Alex.
Received on Wed Sep 24 2008 - 17:43:55 MDT