Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:49248 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35513 invoked from network); 10 Aug 2010 09:43:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Aug 2010 09:43:57 -0000 Authentication-Results: pb1.pair.com header.from=johannes@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 217.114.211.66 as permitted sender) X-PHP-List-Original-Sender: johannes@php.net X-Host-Fingerprint: 217.114.211.66 ns.km36107.keymachine.de Solaris 10 (beta) Received: from [217.114.211.66] ([217.114.211.66:33196] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 57/04-14965-C5F116C4 for ; Tue, 10 Aug 2010 05:43:56 -0400 Received: from [192.168.1.31] (ppp-93-104-43-196.dynamic.mnet-online.de [93.104.43.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id 5762824ACF; Tue, 10 Aug 2010 11:43:52 +0200 (CEST) To: Adam Harvey Cc: Pierre Joye , Kalle Sommer Nielsen , Internals In-Reply-To: References: <1281429940.969.2093.camel@guybrush> Content-Type: text/plain; charset="UTF-8" Organization: php.net Date: Tue, 10 Aug 2010 11:43:51 +0200 Message-ID: <1281433431.969.2220.camel@guybrush> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] 5.4 Alpha? From: johannes@php.net (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Tue, 2010-08-10 at 17:25 +0800, Adam Harvey wrote: > – The LTS branch is going to become more and more difficult to > backport fixes to as it diverges from the other two branches, and I > can see developers not bothering after a certain point, which may be > counter productive. Except for things like the Unicode branch our code base is quite stable in most places. > – Documenting how functionality changes from version to version in the > manual is already a weak point, judging by some of the bugs and > feedback we get: users don't always grok the version bylines and > change log tables in the function reference as it is, and that's with > a more closely aligned set of active branches. We might end up needing > to rethink how we structure the manual by looking at something like > the Python approach of having separate manuals for separate versions, > which would require a not-insignificant amount of work. In the LTS the functionality shouldn't change (having shorter cycles even between other bug fix releases) Yes there are exceptions where a needed bug fix has an effect, but documenting this should be solvable. > – It might be hard to communicate why 5.4 (in the example you > included) becomes end of lifed while 5.3 lives on. I guess that's no > different to Ubuntu, though. Better naming than simply "5.3", "5.4" ... might help. But should be solvable. > – Will downstream distributors want to ship non-LTS versions? This > might actually reduce the amount of useful feedback we get for (again, > using your example) 5.4, 5.5 and 5.6 releases, which might not be a > great thing for the stability of the next LTS (6.0) release. Distributors should be able to distribute two versions. Some do/did with PHP 4 and PHP 5. And I prefer distributions offering the bug fix releases for the LTS version over a heavily patched outdated 5.1.6 like RedHat does. johannes