Re: [RFC] 3.1 branching

On Thu, 2008-09-25 at 01:21 +0200, Henrik Nordstrom wrote:
> On ons, 2008-09-24 at 13:56 -0600, Alex Rousskov wrote:
> > Cool. So, if there are no objections, we have:
> >
> > 0) Trunk is usually open for new stuff. Make daily snapshots.
> > 1) Branch X.Y when major features are committed. Snapshots.
> > 2a) Release X.Y.0.0 when all major bugs are fixed.
> > 2b) Release X.Y.0.w as code gets better, w >= 1.
> > 3a) Release X.Y.1 when the last X.Y.0.w was "stable". Mark branch as stable.
> > 3b) Release X.Y.z as bugs get fixed, z > 1.
>
> Sounds good to me, but see below for a minor adjustment and reasoning.

<good stuff snipped>

> So we have
>
> 1. Branch when trunk is considered a suitable startingpoint for getting
> to stable, and tag a x.y.0 release at the branchpoint (or at least set
> this version in configure.in).
>
> 2a. Release X.Y.0.1 when ready for testing
> 2b. Release X.Y.0.w as code gets better, w > 1

+1

Alex.
Received on Wed Sep 24 2008 - 23:31:34 MDT