William A. Rowe, Jr. wrote:
...
> And once it survives the daedalus stress test we should be all set
> for a pretty thorough beta. Things finally look quite stable,
> development
> wise, and we have a few folks interested in exploring those 'deferred for
> 2.1/3.0' sorts of features. Not that 2.0 bugfixing should come to some
> abrupt halt - only that 2.0 should become a stable tree, and new growth
> should start occuring on 2.1/3.0 type trees, depending on how radical
> the surgery that's required.
Based on the apparent good condition of 2.0.34, I'm
starting to think of 2.0.35 as a likely GA candidate.
The things I know of that should be in a GA release are:
* Cliff's bucket allocator speedup patch
* Any additional perchild fixes that might be needed
* A fix for the mod_include segfault problem that Paul
Reder is investigating
* And any miscellaneous bugfixes that happen between
now and then.
Am I missing anything? Based on that list, I estimate
that we could be ready to tag 2.0.35 in a week or two,
assuming no major problems emerge in .34.
--Brian
