On 10.11.2015, at 10:26, Lester Caine <les...@lsces.co.uk> wrote: > > On 10/11/15 00:49, Rasmus Lerdorf wrote: >>> November 30 is Cyber Monday, where people are either >>>> >>>> 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) >>>> >>>> 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. >>>> >>>> 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. >> >> 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. > > 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 ">=5.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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
