Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:89687 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 33629 invoked from network); 7 Dec 2015 05:21:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Dec 2015 05:21:23 -0000 Authentication-Results: pb1.pair.com smtp.mail=larry@garfieldtech.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=larry@garfieldtech.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 66.111.4.28 cause and error) X-PHP-List-Original-Sender: larry@garfieldtech.com X-Host-Fingerprint: 66.111.4.28 out4-smtp.messagingengine.com Received: from [66.111.4.28] ([66.111.4.28:59807] helo=out4-smtp.messagingengine.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7E/C9-55814-25715665 for ; Mon, 07 Dec 2015 00:21:22 -0500 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 0AA2E20883 for ; Mon, 7 Dec 2015 00:21:20 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Mon, 07 Dec 2015 00:21:20 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=XAks7+LWhf3lmut lYbRB4w8QvhU=; b=KZ1tzR/JkVCzP0aQH57qWUr6E9PLivg4B/3H2BpB615V+7u DTF09Gp8yO8nhQTz1LuDt2zn+6hLgKrgWNkDU+CrEq3fAlmFMUPbfdrVhA+kBdmA XsUdJqmMEMhalbDUFA6JTWVmHIfJqTd2B4tQP6CT+NWF+27k2IWQoAvf6N8I= X-Sasl-enc: lN9p6b732u/R23XwX+OpmL9EpCDPFMQLew/7xzxMYfaD 1449465679 Received: from [192.168.42.5] (c-50-178-40-84.hsd1.il.comcast.net [50.178.40.84]) by mail.messagingengine.com (Postfix) with ESMTPA id B1DC6C01791 for ; Mon, 7 Dec 2015 00:21:19 -0500 (EST) To: internals@lists.php.net References: <90c8ecbc29f8a40a2430306b807a169e@mail.gmail.com> <5664AC01.1020602@gmail.com> <5664C221.9040403@gmail.com> Message-ID: <5665174E.9000202@garfieldtech.com> Date: Sun, 6 Dec 2015 23:21:18 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP 5.6 life cycle From: larry@garfieldtech.com (Larry Garfield) On 12/06/2015 06:02 PM, Jan Ehrhardt wrote: > Stanislav Malyshev in php.internals (Sun, 6 Dec 2015 15:17:53 -0800): >> Hi! >> >>> Giving everyone until the end of 2017 to update their servers is more >>> than sufficient. >> Sufficient for what? It is a hard fact that people still run 5.3 >> version. In fact, 2/3 of sites run EOLed versions. > I know why *we* are still running PHP 5.3 for some sites: they are Drupal6 > sites. Last time we checked it, PHP 5.4 gave all kinds of warnings with > Drupal6 and PHP 5.3 did not. > > Legacy sites? Yes, but not that much. We had been waiting for Drupal8 to > upgrade, but Drupal8 was postponed and postponed and... (Sorry, Larry). > Now it is finally released. No offense taken. :-) Although my Drupal 6 blog (www.garfieldtech.com) is running successfully on PHP 5.6 right now. You just have to make sure you're on the latest version of core and contrib modules. I do not know what Drupal 6's PHP 7 status is, although Drupal 6 support ends 1 March, I believe. Drupal 7 mostly works but has a few test failures we'll be looking into shortly. --Larry Garfield