Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79673
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain bof.de designates 80.242.145.70 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <b5c38ff73acf6a79f2541dd693d5366f@mail.gmail.com>
References: <CAMUwpuRZRb3z+gkU1ejctvfHGc_K=zWxSYmQn=TxVX9zS+fD0A@mail.gmail.com>
	<30315309863fc1883f187e2f6777d081@mail.gmail.com>
	<CAFMT4Npp+JpKvyJ5L75_w9rFipwdbtRNmBX4sdtT8jUo2G2bew@mail.gmail.com>
	<cca63350a40e7c9a9d7fbca3f836ac31@mail.gmail.com>
	<CADajX4BBPFYpZ2-Q_zsk9ft5q+CQE6oZ9fQHO1_bfVn37mcPKg@mail.gmail.com>
	<b5c38ff73acf6a79f2541dd693d5366f@mail.gmail.com>
Date: Mon, 15 Dec 2014 21:36:33 +0100
Message-ID: <CAJ26g5TWVfP9ErgxVWQw-Z3CUeySPgkAyaZpU6tzaV3O+J2=Vw@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: internals <internals@lists.php.net>, Adam Harvey <adam@adamharvey.name>
Content-Type: multipart/alternative; boundary=001a11c11da6bc849b050a47323d
Subject: RE: [PHP-DEV] On the road to PHP 5.7 , or not ?
From: php@bof.de (Patrick Schaaf)

--001a11c11da6bc849b050a47323d
Content-Type: text/plain; charset=UTF-8

Am 15.12.2014 20:43 schrieb "Zeev Suraski" <zeev@zend.com>:
>
> The extra pain associated with migrating to an interim
> version - that does nothing but spew warnings in the right places -and
> obviously doesn't have any of the other features of 7 - doesn't seem to
be a
> worthwhile experience for most users.

I dont't know about "most users", I can only speak for myself from our
small shop (in the big scheme of things...) production and development
experience. I compile PHP myself for our setup, and have a nice compilation
and deployment environment where I can easily throw new versions separately
onto developer hosts and production hosts. We made our codebase
E_STRICT|E_DEPRECATED-clean on the transition from 5.3 to 5.4, meanwhile
migrated to 5.5, and soon to 5.6, with almost no pain, by first running new
versions on developer machines and then on one of several production
servers, where possibly issues are visible pretty fast.

Now with PHP 7 promising potential for incompatibilities in a lot more
areas, it would be, to us, a really useful option to have a 5.7 that is
operationally fully compatible with 5.6 with added E_DEPRECATED for things
bound to break. With that we could A) rub the developers' noses in the
relevant deprecation messages for a while, _and_ run one or more rounds of
one-of-the-production -server tests, gathering more deprecation messages
there without fear of user visible effects.

I cannot judge how much effort such a 5.7 would be for you as developers,
and for the release managers, but I definitely would appreciate the effort,
and I'm 100% sure that it would speed up our eventual adoption of PHP 7 by
at least half a year, because the process would be much less risky.

best regards
  Patrick

--001a11c11da6bc849b050a47323d--