On Dec 16, 2014 9:10 PM, "Zeev Suraski" <z...@zend.com> wrote: > > > -----Original Message----- > > From: Andrea Faulds [mailto:a...@ajf.me] > > Sent: Tuesday, December 16, 2014 10:00 AM > > To: Ferenc Kovacs > > Cc: Matteo Beccati; Xinchen Hui; PHP Internals > > Subject: Re: [PHP-DEV] [RFC] PHP 5.7 > > > > Hey, > > > > > On 16 Dec 2014, at 07:58, Ferenc Kovacs <tyr...@gmail.com> wrote: > > > > > > We already has one accepted RFC which targets 5.7, and as I mentioned > > before 5.7.0 wouldn't be featureless, but would contain the small self- > > contained features which are currently targeting 5.6.x. > > > So 5.7.0 would be a minor version without new major features, but also > > > no > > BC break, would allow us to make 5.6 more stable, and be a stepping stone > > for 7.0 with the deprecated errors. > > > > That’s a benefit I hadn’t considered: people using distros are stuck on a > > specific micro, so anything added to 5.6.x they’ll be able to get with > > 5.7.0, > > right? > > I'm missing what benefit this gives us. > > Distros lock the version (all 3 digits) for a particular distro version; At > the same time, when a new version of the distro comes out, there are no > version restrictions of any kind. > > So for a given distro that uses 5.6.8 (as an example), upgrading to 5.6.9 or > 5.7.0 or even 7.0.0 is equally forbidden within the same distro version, and > equally allowed within a new distro version.
And given that many distros have a faster adoption rate, many will adopt 5.7, with notifications for the 7 changes, in their next release as they may be more looking for 6.1 than 6.0. To support this fact, see the recent adoption rate of all major versions since we adopted the release process RFC. One of its goal has been achieved.
