Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55746
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.127 cause and error)
Message-ID: <4E9001FC.2000507@lsces.co.uk>
Date: Sat, 08 Oct 2011 08:55:40 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0.2) Gecko/20110907 Firefox/6.0.2 SeaMonkey/2.3.3
MIME-Version: 1.0
To: PHP Internals <internals@lists.php.net>
References: <CAH-PCH7ifnqWsCcK6PXfp2BodnxaazqZjqpmdVDRcDgnodwLHg@mail.gmail.com> <CAEZPtU5HzURdjnwY0ncreHVQJj6EtNJG5mf4WEYTP70bpP+6UQ@mail.gmail.com>
In-Reply-To: <CAEZPtU5HzURdjnwY0ncreHVQJj6EtNJG5mf4WEYTP70bpP+6UQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] little tweeking on the release process RFC
From: lester@lsces.co.uk (Lester Caine)

Pierre Joye wrote:
>> "No feature addition after final x.y.0 release (or x.0.0). Self
>> >  contained features or new SAPIs could be carefully considered on a
>> >  case by case basis."
>> >  I would re-phrase the No feature addition to changing existing
>> >  behavior, as it now seems a little bit contradictional.
> I don't see how it is contradictory. SAPIs are self contained and
> can't harm another SAPI, that's why we added this clause.

This is where the modular/bundled discussion comes in? Anything that is bundled 
has to be nailed down, but creating a new extension, or SAPI that is shipped 
separately is a different matter? Even creating a variation of a currently 
bundled extension such as a major update to a linked library need not impinge on 
the core and should not need every other extension to be updated!

I'm still of the opinion that there should be more unbundling, then areas like 
the current debate on MySQL support can be ring fenced to that set of 
extensions. They are not a core requirement therefore can be left out. ANY 
changes which bridge the gap between extensions should perhaps be restricted to 
X.0.0 level anyway. Certainly any bug in an extension which requires the core to 
be modified to be fixed would indicate a coding problem that needs addressing?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php