RE: [PEAR-DEV] [RFC_v3] Handling Backwards Compatibility in PEAR [hopefully the final draft]
| From: | Lukas Smith | Date: | Fri, 26 Sep 2003 06:43:57 +0000 |
| Subject: | RE: [PEAR-DEV] [RFC_v3] Handling Backwards Compatibility in PEAR [hopefully the final draft] | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-22056@lists.php.net to get a copy of this message | ||
> From: Greg Beaver [mailto:greg@chiaraquartet.net]
> Sent: Thursday, September 25, 2003 5:32 PM
>
> Tomas V.V.Cox wrote:
>
> >>The Solution:
> >>------------
> >>The API of a PEAR package may only break BC if:
> >
> >
> >>1) The packages is in the preparation phase to a new major version
> number
> >>2) A new major stable release is made
> >
> >
> > I see no difference between these two points. I guess you can merge
> > them safely. No BC is allowed if no major version is bumped. The 1)
> > invites to think that in 1.9beta they can break the api.
>
> I agree with this.
I guess that I wanted to say was that you can break BC in 2.0 beta
however you cannot break BC in 2.1 beta.
Also you can break BC all you want in the pre 1.x phase.
Regards,
Lukas