I welcome new releases, but what happened to the releaseplan (announced last spring) for 1.6, and what happened to release 1.5.2? What's really needed is a proper release policy, aimed at regularly scheduled milestone releases and a consistent output of maintenance releases. Lacking this, there is not a single MMBase release available at present, that is ready for production, at least not in the projects I have done recently. A bad situation in my opinion, and I don't think ad hoc codefreezes, as you propose, are a significant contribution to improve this. I would like to see a more structural approach. Is this what the disto project is for? Or the foundation?
Rob van Maris Developer Finalist IT Group Java Specialists ------------------------------------------------------------- Amsterdam, The Netherlands Office: +31 20 5962321 (Direct) Mobile: +31 651444006 Fax: +31 20 5962331 -------------------------------------------------------------
