Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62926
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.170 as permitted sender)
MIME-Version: 1.0
Sender: amaury.bouchard@gmail.com
In-Reply-To: <CAMUwpuRdHMmbYSj1nqbKSdV=23SA20J0udaU-CYmHBRbZ40NeQ@mail.gmail.com>
References: <CAMUwpuRdHMmbYSj1nqbKSdV=23SA20J0udaU-CYmHBRbZ40NeQ@mail.gmail.com>
Date: Mon, 10 Sep 2012 19:10:16 +0200
Message-ID: <CAPaKmR=eSvNUxGbbBxp_XvWHubKGPPRaX28dth6aL8VzOs+=4g@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: amaury@amaury.net (Amaury Bouchard)

2012/9/10 jpauli <jpauli@php.net>:
> 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.
>
>
> What could be qualified as a BCB ?

Any modification that change the behaviour of an existing API?

Most of libraries change their minor version number when they add a
new interface, but they change their major number when an existing
interface is modified.