Re: [PEPr] Comment on RFC::Drop requirement of renaming a package when migrating from PHP 4.x to PHP 5.x
| From: | Jon Parise | Date: | Sat, 25 Jul 2009 21:32:18 +0000 |
| Subject: | Re: [PEPr] Comment on RFC::Drop requirement of renaming a package when migrating from PHP 4.x to PHP 5.x | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-52484@lists.php.net to get a copy of this message | ||
On Jul 25, 2009, at 1:50 PM, Brett Bieber wrote:
I think the title of this RFC is incorrect. I'm not aware of any requirement to rename a package when migrating from PHP4 to PHP5 - the standards state that once a package has reached 'stable,' breaking backwards compatibility requires changing the package name. I don't believe this has anything to do with what PHP version the package requires.This is the primarily reason why I have yet to release a version of the Log package that supports PHP5's features and language extensions. I would like to call such a new version Log 2.0, but I believe that the current rules would require me to create a new Log2 package to do so. My preference would be to use the package version, API version, and PHP version to manage all of those dependencies within the package.xml and pear.php.net infrastructure. -- Jon Parise (jon of php.net) :: The PHP Project (http://www.php.net/)