Re: PHP5 Version of Existing Package
| From: | Justin Patrin | Date: | Wed, 02 Mar 2005 19:41:01 +0000 |
| Subject: | Re: PHP5 Version of Existing Package | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-36489@lists.php.net to get a copy of this message | ||
On Wed, 02 Mar 2005 14:31:45 -0500, Scott Mattocks <scott@crisscott.com> wrote:
> Hello,
>
> I am sure this topic has been discussed before but I can't seem to find
> a definitive answer anywhere. What are the rules about releasing a PHP5
> only version of an existing package?
>
> Two of my packages are PHP-GTK packages. When I update them to work with
> PHP-GTK2, which requires PHP5, it will not be possible to make them
> backward compatible. When I update Gtk_ScrollingLabel, do I need to
> create a new package called Gtk_ScrollingLabel2 like we have with
> PHPUnit and PHPUnit2 or should I release it as Gtk_ScrollingLabel 2.0.0?
> The new version will be the same API just a slightly different
> implementation and will require PHP-GTK2 instead of PHP-GTK1.
>
If you're updating a PHP4 compatible package to be PHP5 only that
breaks BC whether or not the API changes. Therefore the package should
be Package2 2.0.0 (once stable)
Package 2.0.0 is *not valid*. All major version # revisions are
assumed to have BC breaks and so must be a new package. If you don't
break BC you should stay with the same version # (but as I said
earlier, switching from PHP4 to PHP5 is a BC break).
--
Justin Patrin