Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62927
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAMUwpuRdHMmbYSj1nqbKSdV=23SA20J0udaU-CYmHBRbZ40NeQ@mail.gmail.com>
References: <CAMUwpuRdHMmbYSj1nqbKSdV=23SA20J0udaU-CYmHBRbZ40NeQ@mail.gmail.com>
Date: Mon, 10 Sep 2012 19:54:31 +0200
Message-ID: <CAEZPtU7Nue-XVHeeSpt2ff82_F5Y7-vcB38UHoDqaLfY+1BnfQ@mail.gmail.com>
To: jpauli <jpauli@php.net>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] What is our definition of a "Backward Compatibility Break"
From: pierre.php@gmail.com (Pierre Joye)

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