Re: Re: [PEPr] Comment on RFC::Requiring E_STRICT Compatibility for NewPEAR Packages

Hi, Lukas Smith wrote:

The RFC should state that new packages must provide a PHP5 E_STRICT version, but not restrict to that version only.

I sincerely doubt that people would write two versions of packages but if this ever happens... OK, I'll add this idea to the RFC.

Not sure if that is really a good idea. The 2 versions still need to be maintained. Beyond the interest of the given developer. Anyways if we allow PHP4 packages upto a given point, there is nothing from stopping them proposing a PHP4 variant of their package upto that point.

Well, the point of this RFC is encouraging development for PHP5. Thus if we do get an E_STRICT compatible version of a package then I don't really care if we also get a PHP4 version (that version should probably be a separate proposal that should start only after the PHP5 version is accepted). Also it's a bit more fair than your +15 requirement, since that way few developers actually interested in getting the PHP4 version may cause the acceptance of the proposal. Getting +15 is almost impossible.