On 22 November 2015 at 14:19, Rasmus Lerdorf <ras...@lerdorf.com> wrote: > On 11/22/2015 06:18 AM, Anthony Ferrara wrote: >> Zeev, >> >> On Sat, Nov 21, 2015 at 11:52 PM, Zeev Suraski <z...@zend.com> wrote: >>> >>> IMHO, unless we think fixing this would require breaking binary >>> compatibility (which I don't think is the case) - this shouldn't block >>> 7.0.0. 7.0.0 is a lot more about getting people to start paying attention >>> to 7.0 and start testing their codebase against it - finding both the >>> incompatibilities in their code and, undoubtedly - the bugs we failed to >>> find. I wish we could say this would be the last issue we find in 7.0, but >>> I think we can all agree it's wishful thinking...
Sure, but not every issue is created equal. Not being able to trust count() is pretty fundamental — sure, it's not "PHP segfaults when you access a $_GET variable" bad, but it's still bad, and it's the kind of bug that even reasonable unit tests might not find. > I agree with Zeev here and I had a chat with Anatol about this tonight. > This is a .0.0 release. Nobody is going to take a .0.0 and push it > straight to production. And it is not going to part of any sort of LTS > distro either. It's not like LTS distros don't pick up point releases. > There is no way we will go 2 weeks without finding something for quite a > while still which can drag things out indefinitely. The question is > whether this is significant enough to postpone further. Personally I > don't think it is. Let's get 7.0.0 out the door and get ourselves on > track for regular point releases without any of this "perfect-release" > stress. I disagree completely with that. No, sensible people aren't going to push 7.0.0 straight to production, but remember David Zuelke's e-mail from two weeks ago about how Heroku customers with poorly chosen version constraints might end up with it by accident. The world's not as simple as sysadmins running "./configure && make install" any more. As a group, we're saying that 7.0.0 is "stable". That doesn't mean perfect, but it should mean "you can trust count()". Here's an alternative suggestion: we've previously switched to one week RC cycles late in the piece when trying to get major releases stabilised and we're at the point of only fixing one or two things per RC. That's exactly where we are now. Why don't we do that again — release a fix for this bug as an RC 8 this week, and then do a release on December 3 if nothing else significant comes up? Adam -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
