Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89725
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain telia.com from 81.236.60.154 cause and error)
To: Sebastian Bergmann <sebastian@php.net>
References: <d7986bddhrs5d7o2c6r42g6h9to3au5kq0@4ax.com>
 <90c8ecbc29f8a40a2430306b807a169e@mail.gmail.com> <566464A8.7030203@php.net>
 <566468FD.5020001@telia.com> <56646AEE.3070701@php.net>
Cc: PHP internals <internals@lists.php.net>
Message-ID: <5665E1FD.5060300@telia.com>
Date: Mon, 7 Dec 2015 20:46:05 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <56646AEE.3070701@php.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] PHP 5.6 life cycle
From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=)

Den 2015-12-06 kl. 18:05, skrev Sebastian Bergmann:
> Am 06.12.2015 um 17:57 schrieb Björn Larsson:
>> Would like to add that given 7.0 major uptake with ISP's coming next
>> year (at least in my region) it seems prudent to prolong 5.6 lifecycle a
>> little.
>   I fear that extending support for PHP 5 will slow down adoption of
>   PHP 7.
>
Given the high performance boost with PHP 7 I don't think extended support
will delay for ISP's to offer PHP 7 for their customers. It's a very 
good business
case to upgrade. I think it's more about migrating existing environment and
extension support that can delay things.

Regards //Björn