Excerpts from Pierre Joye's message of Wed Sep 21 08:01:48 -0700 2011: > 2011/9/21 Johannes Schlüter <johan...@schlueters.de>: > > > Exactly. (while I, at this time, won't argue which behavior is more > > "correct") changing this in the first place was wrong. Changing it back > > is wrong again. We have two versions out with this change. These > > releases reach distributions, reach hosting companies, reach developer > > machines, ... changing the behavior again causes more trouble. With a > > proper heads up before 5.3.8 we might probably have reverted it there. > > I agree and I seriously hope that we will stop to do such things from > now on and apply the RFC to 5.3 as well.
Just to give some perspective on this, we specifically did not ship php 5.3.8 in Ubuntu 11.10 (in beta right now) because of this confusion. This is in spite of the fact that it would have closed many bugs, and reduced some of the burden on our security team since they are charged with back-porting all security fixes to whatever we ship. I was kind of hoping it would be rolled back rapidly in another release. >From a distribution standpoint, the change in 5.3.8 is a nightmare and will require us to either ship with lots of bugs in the dependent packages, or lots of patches and delta from upstream. Reverting back to the pre 5.3.8 behavior would allow us to ship the new version and move forward with future versions without worry. One question.. if things have been adapted for 5.3.8 .. will they be negatively affected by a rollback to pre 5.3.8 behavior? If not, I'd wonder why there would be any resistance at all to doing this, as it seems more important that 5.3 is consistent from early versions to the latest than it is that one version had a serious problem. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
