RE: [PEAR-DEV] [RFC] BC breakage in PEAR - how to handle it properly
| From: | Lukas Smith | Date: | Thu, 18 Sep 2003 08:15:39 +0000 |
| Subject: | RE: [PEAR-DEV] [RFC] BC breakage in PEAR - how to handle it properly | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-21693@lists.php.net to get a copy of this message | ||
> From: Greg Beaver [mailto:greg@chiaraquartet.net]
> Sent: Thursday, September 18, 2003 2:27 AM
> This is why I think complete rewrites with no BC break should not be
> major version increases - but Lukas and Pierre feel differently. I
> would propose that complete rewrites should be a minor version
increase
> of at least 10, so that 1.2 becomes 1.12. In this way, we can have
Foo
> 1.x and Foo2 2.x
>
> I really think major version increase probably should ONLY be for BC
> breakage, otherwise it's just a huge mess that cannot be automated.
One reason why I say this is that a rewrite should be communicated to
the user. There maybe drastic changes in the behaviour even if there are
no BC breaks:
1. performance
2. quality
3. compatibility of patches
If we find a different way to communicate a rewrite then I don't have a
problem with not requiring a major version increase.
regards,
Lukas