2015-12-07 17:11 GMT+02:00 Zeev Suraski <z...@zend.com>: > > -----Original Message----- > > From: Rowan Collins [mailto:rowan.coll...@gmail.com] > > Sent: Monday, December 07, 2015 4:42 PM > > To: internals@lists.php.net > > Subject: Re: [PHP-DEV] Re: PHP 5.6 life cycle > > > > Rowan Collins wrote on 07/12/2015 14:35: > > > - On what factors will the decision be based? If the reason to delay > > > the decision is lack of information, what information are we planning > > > to use? Are there metrics we can use to make a more objective > decision? > > > > Come to think, this works the other way as well: if we *do* make a > decision > > now, are there factors that would allow the question to be reopened? > Again, > > to have any trust in the announced date, people would need to know what > > these were - if the decision is "probably August 2017", then that would > be no > > decision at all. > > It's always possible to submit another RFC to alter the end date, even if > we decide about one now. But I do think it'll send a different message - > that we think it's going to take extraordinary circumstances for us to > change the decision - vs. us saying "we'll wait and see", which at least I > would interpret as "they'll probably delay it". > > Zeev > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > According to PHP release RFC - the date is already set. To extend support for 5.6 you actually now need an RFC. Without the RFC any decision made by anybody in that regard is invalid and irrelevant.
RFC or didn't happen. Just to be clear people do not forget what they actually voted on and that they have to stick to a process to make decisions.