Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62939
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <504E72E2.9040100@sugarcrm.com>
References: <CAMUwpuRdHMmbYSj1nqbKSdV=23SA20J0udaU-CYmHBRbZ40NeQ@mail.gmail.com>
	<504E72E2.9040100@sugarcrm.com>
Date: Tue, 11 Sep 2012 01:00:58 +0100
Message-ID: <CADNQb0Xw_T3ejr+NT-vrSK_OY_sDXSQhjx-FZHU+aFp6iucXMQ@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: jpauli <jpauli@php.net>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] What is our definition of a "Backward Compatibility Break"
From: hannes.magnusson@gmail.com (Hannes Magnusson)

On Tue, Sep 11, 2012 at 12:08 AM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> Hi!
>
>> 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.
>> Stas' recent topic on internals "On BC and interfaces" may serve as a
>> reflection basis.
>> As our release process told us that we should not add BCB (but only
>> "minor" ones ... hum) in any minor release (nor revision), and as 5.5
>> release process is going to start soon, I'd like we try to all agree
>> on that point.
>
> I think first we have to distinguish several levels of BC:
>
> 1. Binary BC
> 2. Source-level extension BC
> 3. PHP Code (API) BC
>
> Binary BC means that extension compiled with one version would work with
> another without recompilation. We keep this level of compatibility
> through all minor (5.x) releases and breaking it is an absolute no-no.
> However, between minors (5.5 -> 5.5) breaking it is fine.

Typo alert. That should say 5.4 -> 5.5 :)

-Hannes