Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76533 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43542 invoked from network); 15 Aug 2014 01:18:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Aug 2014 01:18:16 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.83 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.83 smtp83.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.83] ([108.166.43.83:40848] helo=smtp83.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E7/90-40673-7DF5DE35 for ; Thu, 14 Aug 2014 21:18:15 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id EC8C4180442; Thu, 14 Aug 2014 21:18:12 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id A2E8A180478; Thu, 14 Aug 2014 21:18:12 -0400 (EDT) X-Sender-Id: smalyshev@sugarcrm.com Received: from Stass-MacBook-Pro.local ([UNAVAILABLE]. [74.85.23.222]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA) by 0.0.0.0:465 (trex/5.2.10); Fri, 15 Aug 2014 01:18:12 GMT Message-ID: <53ED5FD4.7000307@sugarcrm.com> Date: Thu, 14 Aug 2014 18:18:12 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Jan Ehrhardt , "internals@lists.php.net" References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Status of PHP 5.4 From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > PHP 5.3 has reached the real end of life. Will the effect be that from > now on PHP 5.4 will only get security fixes? There's no dependency between the two in the release RFC, but it would probably make sense to move 5.4 into "security only" phase once 5.6 is GA, and set EOL date for 1 year since that moment, as we did with 5.3. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/