Hi Andi, > On 30 Dec 2014, at 21:43, Andi Gutmans <a...@zend.com> wrote: > > My take is that anything that takes away efforts from getting PHP 7 to market > faster is a distraction. > PHP.net needs to continue to show leadership in evolving the runtime. We have > a pretty great jewel in our hands. Some very good RFCs that are going to make > it in. Postponing PHP 7 (which this would as we have a finite amount of > resources on this list) would not be good for our users.
I too want to see PHP 7 as soon as possible, and I too want some great RFCs to get in. (I’m really hoping I can get my bigint RFC in, particularly, given I’ve put so much effort into it. Though there’s a good chance it won’t get in due to time constraints.) However, I don’t think 5.7 would consume much effort or be much of a distraction. Bear in mind that the changeset from 5.6 would be trivial at best, as it would contain zero new features. In fact, this is mandated by the RFC, which specifically prohibits new features. The only time it would really require any more effort is after 5.6’s bug fix support ends, as 5.7 would have normal bug fixes for another year. So, while I understand your concern, I don’t think it would have any effect on PHP 7’s release date. Thanks! -- Andrea Faulds http://ajf.me/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
