Re: PEPr #419: Requiring E_STRICT Compatibility for New PEAR Packages

Markus Tacker wrote:

Referring to: http://pear.php.net/pepr/pepr-proposal-show.php?id=419 I basically like it. But it should state that the next major version of every package is not affected. There may already be development in progress by the time the proposal is accepted.

Well for a start this proposal needs to be moved to the "proposal" phase so that people can comment on it ;) Aside from that we have put in grandfathering rules in past RFC's. There should probably be a phase where people can say what they are already working on. BTW: We already have an RFC IIRC that defines that all PHP5 packages need to be E_STRICT compatible. So the real addition of this RFC seems to be to kill of the development of new PHP4 packages and to set the benchmark for PHP5 compatibility at PHP 5.1.

I think it should also read that a switch from PHP4 to PHP5 object model requires a version increment of the major version number e.g. 1.3 to 2.0.

Moving to a new major version of PHP is considered to be a BC break. regards, Lukas