On Dec 16, 2014 10:23 PM, "Zeev Suraski" <z...@zend.com> wrote: > > > -----Original Message----- > > From: morrison.l...@gmail.com [mailto:morrison.l...@gmail.com] On > > Behalf Of Levi Morrison > > Sent: Tuesday, December 16, 2014 9:29 AM > > To: Xinchen Hui > > Cc: Andrea Faulds; PHP Internals > > Subject: Re: [PHP-DEV] [RFC] PHP 5.7 > > > > >> There has been some debate about whether to make “PHP 5.7". I have > > made a very simple RFC. It proposes a final minor version of PHP 5, PHP > > 5.7, > > to be released at the same time as PHP 7, with no new features whatsoever. > > >> > > > I am wondering why we need that? no new features.... > > > > > > I think we can extend 5.6 release cycle to avoid that.. > > > > Extending the PHP 5.6 release cycle doesn't give an opportunity to raise > > different E_STRICT and E_DEPRECATED messages in preparation for PHP 7.0. > > This may or may not be something you value, but it's something I > > personally > > value. > > I don't see why we'd need new E_STRICT's, but what stops us from adding > E_DEPRECATED to 5.6.x?
We do not allow them or we try to avoid them by all means. > I think the likelihood of getting these notices in the hands of people goes > way higher if we put it into 5.6.x, which will be perceived as a bug-fix > release, than a 5.7.0, which will be perceived as a feature release. And what will be the work load difference then? Zero. However it will introduce changes in a patch release that may not be expected as of our RFC. I am totally opposed to this idea.
