Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79733
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <a8c2a1ebe99c1c5d8a891a984100350d@mail.gmail.com>
References: <8C1EFD82-CFE0-4D01-9231-2A1658B182A6@ajf.me>
	<CABBJUpfLCjWCgOUneN2O2M7qP2WBf8OgbVrdB-jm+Fn_dDJvVA@mail.gmail.com>
	<548FE4A8.4040909@beccati.com>
	<CAH-PCH7iY-WjbL4bKL3dNnrK91AzV3dOEs3FC5kAjD_5zZQBHg@mail.gmail.com>
	<DF203F3D-3653-4856-8BEA-E0981FFBE6DB@ajf.me>
	<a8c2a1ebe99c1c5d8a891a984100350d@mail.gmail.com>
Date: Wed, 17 Dec 2014 04:13:20 +1100
Message-ID: <CAEZPtU5H5JZ9exDfz2QweBupave_cBhcJwiaW83ztnOSLnDWkA@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: Ferenc Kovacs <tyra3l@gmail.com>, PHP internals <internals@lists.php.net>, 
	Xinchen Hui <laruence@php.net>, Andrea Faulds <ajf@ajf.me>, Matteo Beccati <php@beccati.com>
Content-Type: multipart/alternative; boundary=001a11c2d5d4d16521050a58797e
Subject: RE: [PHP-DEV] [RFC] PHP 5.7
From: pierre.php@gmail.com (Pierre Joye)

--001a11c2d5d4d16521050a58797e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Dec 16, 2014 9:10 PM, "Zeev Suraski" <zeev@zend.com> wrote:
>
> > -----Original Message-----
> > From: Andrea Faulds [mailto:ajf@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 <tyra3l@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 als=
o
> > > 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=E2=80=99s a benefit I hadn=E2=80=99t considered: people using dist=
ros are stuck on
a
> > specific micro, so anything added to 5.6.x they=E2=80=99ll be able to g=
et 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=
.

--001a11c2d5d4d16521050a58797e--