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
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
