On Tue, Feb 06, 2001 at 11:44:28AM +0000, Jesper Skov wrote:
> >>>>> "Sam" == Sam TH <[EMAIL PROTECTED]> writes:
> Sam> Our next release (which shouldn't be too far away, barring major
> Sam> catastrophes) will be version 0.9.0 (just like the new
> Sam> splashscreen says). 0.9.0 will be a "feature freeze" release,
> Sam> meaning that after it is release, there will be no new big
> Sam> features. Then, after a few releases of fleshing out missing
> Sam> functionality, and cleaning things up, we have a harder freeze,
> Sam> where nothing goes in that doesn't fix a clear bug. At this
> Sam> point, the tree will probably branch, so that we can start
> Sam> developing wild cool new features again. Then, we eventually
> Sam> pick a candidate off that branch, and release it as 1.0.
>
> Oh no. Please do not consider opening 1.1 until 1.0 has shipped and
> have had a few weeks out there - we're bound to get bug reports from
> new users after 1.0 goes public. And we want full deveoper attention
> on 1.0.x before even considering 1.1
>
> IMO, of course.
<release-manager hat=on>
I'm not sure exactly what you're objecting to here. My current plan
looks like this:
/-- /--
/ /
/---0.9.n+1--//---1.0--1.1--//
/
/-- /-- /
/ / /
------0.9--------0.9.1----//---- 0.9.n
\
\
\ /--
\ /
\-------//--1.1.1----
Do you want the big branch to come _after_ 1.0? If so, I'll think
about that. Of course, none of this is set in stone. Or even in
peanut butter. :-)
</release-manager>
sam th
[EMAIL PROTECTED]
http://www.abisource.com/~sam/
GnuPG Key:
http://www.abisource.com/~sam/key
PGP signature
