Hello Zeev, Monday, May 30, 2005, 5:21:00 PM, you wrote:
> At 18:01 30/05/2005, Wez Furlong wrote: >>If we know the bug, and we have a fix, there shouldn't be anything >>stopping us from making a release. >>If this patch break binary compat, then the only logical move forward >>is a 4.4 branch and release. >> >>I think the question should really be: "why don't we want to give 4.x >>users this bugfix?" >>I can't think of any valid reasons not to do that. > I mentioned two, there are probably more - breaking binary compatibility > (everyone has to rebuild everything, we'll probably have 0.00001C of global > warming on our hands ;), and confusion. We don't break BC here. We simply proceed as we did in the past. And we do this to give the users the best PHP we can. On the other hand all you said pretty much sounds like excuses to not do a new version. But why do you fear that? Too much work - no since we would emmidiatley stop 4.3 support. BC break - no since there simply is none. Everyone has to rebuild - well this is a normal thing and all the windows users are used to simply download the executables and for 95% of the *nix users it is only waiting for new packages. Anybody being able to compile on his own will not have any problem at all since he obviously is capable of building a working php anyway. And the patch addresses some very serious problems. Unfortunatley there are still a bunch of other issues unaddressed by now. To prevent 4.5 from popping up to soon i think we should all take some look into fixing those issues too. Anybody interested in those with a very deeply understanding of the engine should contact Derick, Dmitry or me (working since several weeks on those issues). best regards marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
