Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58533 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 97584 invoked from network); 2 Mar 2012 20:17:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Mar 2012 20:17:48 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.113 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.113 smtp113.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.113] ([67.192.241.113:52228] helo=smtp113.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C6/EF-22821-BEA215F4 for ; Fri, 02 Mar 2012 15:17:48 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp11.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id C825AD0FC9; Fri, 2 Mar 2012 15:17:44 -0500 (EST) X-Virus-Scanned: OK Received: by smtp11.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 71458D0FC5; Fri, 2 Mar 2012 15:17:44 -0500 (EST) Message-ID: <4F512AE7.4060104@sugarcrm.com> Date: Fri, 02 Mar 2012 12:17:43 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1 MIME-Version: 1.0 To: Anthony Ferrara CC: Pierre Joye , Keloran , PHP internals References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] discussions, about a 5.3 EOL From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Would it be worth while to discuss the possibility of LTS releases > (Long Term Support) with 5 or 7 year support (from time of initial > release)...? It is fine to discuss it and you can still support PHP 4 now if you want to, but who's going to be doing it otherwise? I wouldn't really want to spend time on fixing 7-year-old PHP version (that'd be like 4.4 now). So we need to approach it with the view of the resources we have. I hope move to Git will make the technical part much easier (merging patches between branches in git is like 2 orders of magnitude faster), but still one has to spend time on backporting, etc. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227