On Fri, 2002-10-11 at 14:44, [EMAIL PROTECTED] wrote: > I welcome new releases, but what happened to the releaseplan (announced > 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? 1) We really need a new release 2) We need it as soon as possible (better yesterday than now) 3) Would there be volunteers to do this, please do so, otherwise i dont see a better sollution.
The planning of having a freeze, fixing all known bugs, create the release candidate, and making it a release is not a wrong traject (but i agree we would discus about the fact if we really want a candidate) Currently we see more and more organisations using parts of cvs. This should not happen. Delaying the release more will only have as an affect that more organisations will run on cvs instead of on distro's. Furthermore is the 1.5.1 not really supported anymore (do you see bugfix-es in that branche?) Also, having a shorter time frame makes it more interresting for different companies to add hack proposal's to MMBase, or participate in projects, since they can use their own 'things'. Otherwise there is nothing in return for their effort. Currently this is for me one of the highest priorities of things that have to be done.. -- Eduard Witteveen Systeem Ontwikkelaar Publieke Omroep, Gateway C Kamer 101 +31(0)356772910 http://www.omroep.nl/ Sed quis custodiet ipsos custodes? : The sixth Satire from Juvenal
