Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:89649 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19583 invoked from network); 6 Dec 2015 13:21:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Dec 2015 13:21:11 -0000 X-Host-Fingerprint: 85.223.116.227 227-116.citynet.ftth.internl.net Received: from [85.223.116.227] ([85.223.116.227:22091] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 59/53-08340-64634665 for ; Sun, 06 Dec 2015 08:21:10 -0500 To: internals@lists.php.net Date: Sun, 06 Dec 2015 14:21:06 +0100 Message-ID: References: <90c8ecbc29f8a40a2430306b807a169e@mail.gmail.com> X-Newsreader: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Posted-By: 85.223.116.227 Subject: Re: [PHP-DEV] PHP 5.6 life cycle From: phpdev@ehrhardt.nl (Jan Ehrhardt) Zeev Suraski in php.internals (Sun, 6 Dec 2015 14:38:10 +0200): >IMHO, I think we need to look at the 5.6 lifecycle very differently from >how we look at 5.5 and earlier. This is really the 5.x lifecycle as it's >the last version that's relatively completely painless to upgrade to from >5.x (especially 5.3 and later). There is a reason to treat it differently: extension support. Upgrading the core and core extensions is relatively painless. Many popular extensions are rapidly moving towards PHP7 support. But there must be thousands of extensions out there, that we have no knowledge of. For people that have already done a port to PHP7 the next one is relatively simple. But porting your first one has a steep learning curve. -- Jan