Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89151
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain heroku.com designates 74.125.82.47 as permitted sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
In-Reply-To: <5641B835.3060005@lsces.co.uk>
Date: Tue, 10 Nov 2015 17:53:21 +0100
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <6D2A8E66-66A8-4E0D-8622-4C98242FBCE8@heroku.com>
References: <01a501d11a59$d1cba210$7562e630$@belski.net> <563FA66B.1090305@gmail.com> <01fd01d11a8c$3a59c3c0$af0d4b40$@belski.net> <563FF86C.2060007@lerdorf.com> <7FCBAA90-7D7C-49A5-B8A2-B8662EB6AB50@zend.com> <A8CAD009-F5C1-4822-91E8-7080ACA90CA1@heroku.com> <56413F24.7010200@lerdorf.com> <5641B835.3060005@lsces.co.uk>
To: Lester Caine <lester@lsces.co.uk>
Subject: Re: [PHP-DEV] PHP 7 RTM date
From: dz@heroku.com (David Zuelke)

On 10.11.2015, at 10:26, Lester Caine <lester@lsces.co.uk> wrote:
>=20
> On 10/11/15 00:49, Rasmus Lerdorf wrote:
>>> November 30 is Cyber Monday, where people are either
>>>>=20
>>>> a) focused on maxing out their credit cards on every possible =
e-commerce site, or
>>>> b) unable to roll out PHP 7 because their customers are busy with =
a)
>>>>=20
>>>> At least at Heroku we have a blackout policy around Thanksgiving =
and Christmas for platform changes, and I'd imagine other hosting =
platforms do as well.
>>>>=20
>>>> So maybe either Tuesday, or even better, Thursday, since that's =
release day anyway.
>> Let's be realistic. This is not a critical security fix for =
production
>> servers. This is a .0.0 release. For developers this marks the point
>> where they need to start making upgrade plans if they haven't =
already. I
>> realize for Heroku and the few similar cloud computing services out
>> there it might be slightly different in that you want to be quick to
>> provide the first golden PHP 7 to your customers.
>>=20
>> My only concern with the timing is whether we are adding undue
>> inconvenience to our RM team and all the other folks on our side that
>> are affected by a release.
>=20
> Anybody moving their current stable infrastructure to PHP7 without =
fully
> testing deserves everything they get? PHP7 should be 'rolled out' as a
> secondary option for savy users who understand the implications since
> the code base WILL need to be reworked before it becomes a stable
> replacement for the current PhP5.x infrastructure. Actually a cloud
> service getting something out as a taster for PHP7 before the holiday
> could only be helpful since it would give more eyes on real world
> migration problems in much the same way that PHP5 roll-out was =
probably
> helped by RC's being available on some hosting services back then. ARE
> any cloud services providing that facility today with PHP7 RC's?

Sure: http://phpversions.info/paas-hosting/

The default PHP version in the absence of any explicit declaration on =
Heroku will remain 5.6.latest for a while, but if you have a =
composer.json with a bunch of requirements for package "php" like =
">=3D5.3.3", and not a single one with an upper bound, then on the day =
we make PHP 7.0.0 available, your next deploy will get PHP 7, because =
your composer.json says that's fine (unless you also require extensions =
that are not PHP 7 ready; it all gets resolved correctly).

Of course, I'll roll out a warning soon to remind users of this, but =
many will miss it because they tend to never read what's on their =
screens, so the more stable 7.0.0 is, the better!

You'd be surprised how many of our users have composer.json templates =
from weirdo frameworks with "minimum-stability": "dev", and they don't =
even notice that they're getting PHP 7 RCs because of that.

David