People have been asking me when they can get a "stable" version that
includes JavaDX.   I think it'd be a good idea to put out a new tarball
sometime soon that incorporates bug fixes on top of 4.0.9, test it, and
then anoint it golden at 4.1.0.  What I'd like to do is to get everyone to
check in the fixes they are sitting on, then freeze CVS and label it as
4.0.10.  We'd then roll a new tarball that people could test in concert.
If any serious problems show up, we'd very carefully fix them in the CVS
and, when it seems to stabilize again, iterate.  Then label it as 4.1.0,
pronounce it golden, and open the CVS for development again.

What do y'all think?  Are there major unfixed problems that need dealing
with first?  If so, I've lost track - how about posting them?
I'll check the bugs database, too.    How about opinions on timing?

By the way, I don't mean to imply actually locking out CVS commits - just
ask people to hold off on things that can be held off.

Bll tells me I don't misspell enough to be taken seriously as a computer
guy.

Greg

Reply via email to