Re: release policy

[Gary V. Vaughan]

Hi Peter,

Peter O'Gorman wrote:
> Gary V. Vaughan wrote:
> |>>We can always choose to stick with a troublesome stable branch for
> |>>longer if it turns out to need more work to iron out any bugs and
> |>>regressions rather than ploughing on with another head release...
> |>>thoughts?
> |>
> |>
> |>Yes, just one: this is INSANE.
> 
> I like the idea (stolen from gcc) of deciding at the start what features
> need to go into the next feature release, and not allowing others to be
> added until after release. Features can, of course, be removed.
> 
> By limiting the number/scope of features in each release a more frequent
> release schedule is possible.
> 
> Does this sound reasonable?

Yes, certainly.  And it is not incompatible with a time based release
system -- in fact, gnome and gentoo work this way, and make regular
timely releases as a result.

How often do you think we should be aiming to make a release?  Is my
idea of one alpha, one feature, one stable and one maintenance release,
per branch, per year truly barking mad?

Cheers,
        Gary.
-- 
Gary V. Vaughan      ())_.  address@hidden,gnu.org}
Research Scientist   ( '/   http://tkd.kicks-ass.net
GNU Hacker           / )=   http://www.gnu.org/software/libtool
Technical Author   `(_~)_   http://sources.redhat.com/autobook

signature.asc
Description: OpenPGP digital signature