Mail Archives: djgpp-workers/2002/06/13/14:28:51
> The main issue, as Charles points out, is to find a
> victim^H^H^H^H^Holunteer who will manage the release through the alpha
> and beta testing. Once we have that person in charge, we can simply
> produce the first alpha and start the release process.
Andrew has done a great job of building many of the applications with
the CVS code to shake out issues; we are probably in an alpha test
state already, maybe even beta - but since the scope and feature set
is continuously changing it's hard to say.
What's been lacking is a plan - why are we doing a release? I really
don't like declaring that what happens to be checked in today is
a release... If we set a target date, and what the major features
we would like to have in it - it becomes clear what needs to be
done to release or not.
> IMHO, v2.04 has enough new features to justify a release _now_.
I think there should have been one sooner, but ... if we're going to
do one let's not plan to do another one for year or so after. If
you think that way, I'd like to get a few more fixes in.
> From experience, even a simple bugfix release (like v2.03) takes about 9
> months. That's enough time to include and test all the newer features
> like those you mention above and still be left with plenty of
> opportunities to test them.
I was thinking a "target" of December 2002/January 2003 time frame.
Next step is scope - when do we feature freeze vs. bug fix freeze?
And of course, we need the project manager :-)
- Raw text -