4.2 BETA?

[Brian J. Tarricone]

Biju Chacko wrote:

> What are the outstanding issues for 4.2-BETA? My general feeling is 
> that we should release either 4.2.0pre1 (or 4.1.0) immediately with 
> whatever state CVS HEAD is in now. That should be followed up with 
> additional BETA releases every fortnight until we have a consensus 
> that 4.2 is releaseable. Roughly, we should be targetting Oct 31 as a 
> release date for 4.2.

a slight digression that doesn't actually answer your question.  this 
type of thing is where bugzilla shines (if used properly).  you can 
create a set of flags and nominate bugs as blockers for a particular 
release or milestone.  i've never actually set it up, so i'd have to 
read through the docs, but it seems like a rather powerful system.  this 
of course assumes that all the issues at hand are in bugzilla, rather 
than in the dev's head, or discussed on the ML, or something like that.  
biju, since you're Release Man now, i just tossed some more bugzilla 
privs at you; if you want to mess with the flags system at some point, 
feel free.

to actually answer your question, i don't think there's anything 
outstanding that can block a 4.2 beta right now.  current CVS is pretty 
solid, ad least with the limited distribution its gotten so far (which 
is probably not as limited as one would think, since it's been so long 
since a stable release).  so yeah, now is as good a time as any (from my 
perspective, anyway).

> To achieve that, we should have a hard feature freeze starting now. 
> Anything that is not in working condition in CVS HEAD should either be 
> fixed immediately or removed. I don't think there's anything like that 
> though ... CVS seems fairly solid to me.

*nods*

    -brian