At 04:33 AM 4/18/2002, Sander Striker wrote: >There have been several bug fixes since 2.0.35, >the community should benefit from that IMO.
No doubt :) >What is the current status on 2.0.36-dev? I just let a nightly binary build fly on ~wrowe/ that I've posted in response to certain bugfixes nobody on this list ever reproduced (win32 socket problems and other cgi/scriptinterpreter fooness.) Hope to have some feedback quickly! >Greg (Ames), can you holler when you've >seen daedalus run for 3 days without dumping >core? ;) I was under the impression we are still running a near-.35 with specific bugfixes. After those patches prove themselves, it probably will be time to bump to head. [But I could just be confused :-] >I'm bringing this up because I don't want us >to end up with the same release rate we had >for the betas. Better to release often IMO. Wholeheartedly agreed here. Every two to four weeks would seem about ideal, one to three weeks of bugfixes and a week of stabilization should help folks accept the new codebase as solid and building on that. If I can get that semantics change done on optional fns/hooks so we can avoid all mmn version bumps for optional fn/hooks, I think that would also cut down on the bumps for foreign modules. Will look to make some progress and post an example patch by Friday morning.
