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

Hi, 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.

Starting the development of a new major version includes registering a new package on PEAR website. If such a package was registered, then we consider the development started (and this new version is an "existing package" for the purpose of the RFC), if it wasn't then we have no means to find out. We can also consider the presence of code in PEAR CVS.

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.

I thought it is obvious. We need to increment major version if we break BC and this will most like be a BC break, as Lukas already mentioned.