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

From: Date: Mon, 10 Jul 2006 10:22:20 +0000
Subject: Re: Re: [PEPr] Comment on RFC::Requiring E_STRICT Compatibility for New PEAR Packages
References: 1 2 3  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-43310@lists.php.net to get a copy of this message
Hi, Lukas Kahwe Smith wrote:
No, the whole purpose of this RFC is to discourage development of new packages for PHP4 and to encourage moving the existing packages to PHP5 versions. Adding this option defeats the purpose. There are two possibilities of a PHP4 package proposal: 1) A PEARified version of an existing library is proposed. Fortunately we have channels now and the author can distribute this library from his own site. 2) This is indeed a new package. There is no sense starting development in PHP4 if the package may stabilize only when PHP4 is completely obsolete. We won't accept PHP3 package, even if it gains a whopping +50 on PEPr, will we?
No, but PHP3 is obsolete. While PHP4 will not _become_ obsolete in the next 3 years. I think that maybe in 2 years the bulk of development will have moved to PHP5. So I expect still atleast 1 strong year for PHP4.
You couldn't submit a PHP3 package into PEAR when PEAR was just starting, and back then PHP3 was *far* from obsolete. I do understand that PHP4 packages will still be used and existing ones need to be supported. But I don't see benefit in welcoming *new* development for PHP4 right now, only harm. Do you?

« previous php.pear.dev (#43310) next »