I was talking about technical reasons against 4.4, not about breaking the binary signature of 4.3 I don't think confusion is a good reason to not release a bug-fixed version of PHP.
So, what's stopping the PHP project from kicking out 4.4? --Wez. On 5/30/05, Zeev Suraski <[EMAIL PROTECTED]> 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. > > These reasons are not absolute. For instance, if it was a remote exploit > we were dealing with - then obviously security takes precedence over these > arguments. But it isn't. It's a bug that is pretty uncommon and can be > worked around in userspace. Yes, it's annoying if you bump into it, but in > the scale of severity, I don't think it rates very high. > > Zeev > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
