Re: [RFC] BC breakage in PEAR - how to handle it properly
| From: | Marshall Roch | Date: | Thu, 18 Sep 2003 12:24:40 +0000 |
| Subject: | Re: [RFC] BC breakage in PEAR - how to handle it properly | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-21701@lists.php.net to get a copy of this message | ||
Jan Schneider wrote:
Releasing Foo2 *would* break BC with Foo, no matter what, since PEAR naming conventions would require Foo_Example_Class to become Foo2_Example_Class. So if package Foo2 is bc with Foo, and package Bar has 10 files (drivers?) specifically using Foo, then the Bar maintainer has to update all of those files to specifically call Foo2 instead? Seems like a pain... I don't have any solutions, but I wanted to voice the problems I see. -- Marshall Roch http://pear.php.net/user/mrochI really think major version increase probably should ONLY be for BC breakage, otherwise it's just a huge mess that cannot be automated.Why? If the developer feels like he wants to make a clear cut with his rewrite, let him so. It wouldn't break anything. The proposed changes want to make sure that no BC breaks happen within one package lifetime. That doesn't mean that you are not allowed to end a package's lifetime if you don't break BC.