Re: What is our definition of a "Backward Compatibility Break"
| From: | Pierre Joye | Date: | Mon, 10 Sep 2012 17:54:31 +0000 |
| Subject: | Re: What is our definition of a "Backward Compatibility Break" | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-62927@lists.php.net to get a copy of this message | ||
hi,
On Mon, Sep 10, 2012 at 6:28 PM, jpauli <jpauli@php.net> wrote:
> Based on our recent discussion on #pecl , I'd like we clarify what we
> think is a "BCB" (Backward Compatibility Break) as well as what "only
> minor BC breaks" could mean.
Change in phpinfo related stuff are minor. Adding a notice or warning
is minor or irrelevant. Changing return values (like suddenly
returning array instead of integer, f.e.), behaviors or similar things
are not allowed in x.y+1.
> Stas' recent topic on internals "On BC and interfaces" may serve as a
> reflection basis.
That's more about internals APIs, which is not what is meant in the
release RFCs for x.y+1 releases.
Cheers,
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org