Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50620
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=go4q5WrRgy6kCKgOzeL1he3VIpNXri15HFCSBJh5tLn8WUjSWLFAwlSnhhphOGWCgG
         wdR4pduBBpumWzv3TftQQ9wxTbQ3s7dIIOADptOO+hxG3t7VcjWiQfUrHlBZ2H1k/x1d
         NXTCd+Rj8cnv+bwiU6uyaykTEF9A0g/2EA3yI=
MIME-Version: 1.0
In-Reply-To: <AANLkTimVh7GxsLUo03HgJ5J5norCHoBbkT6Z_KyfPuVQ@mail.gmail.com>
References: <AANLkTimVh7GxsLUo03HgJ5J5norCHoBbkT6Z_KyfPuVQ@mail.gmail.com>
Date: Sat, 27 Nov 2010 13:06:02 +0100
Message-ID: <AANLkTinKh3b+JxSGC0PcF=UzoAGbGqPPGbQLTFU72Nus@mail.gmail.com>
To: Karoly Negyesi <karoly@negyesi.net>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Major release for BC??
From: pierre.php@gmail.com (Pierre Joye)

On Sat, Nov 27, 2010 at 12:50 PM, Karoly Negyesi <karoly@negyesi.net> wrote:
> Hi,
>
> I am reading the 5.4 vs 7.0 debate. And, here's something I really
> need to follow up on: "We should reserve major versions for BC breaks.
> Just like we've always done". If that's what you've always done then
> it's not PHP I spent practically every awake minute in the last seven
> or so years.
>
> If backwards compatibility break would mean a new PHP major we would
> be in somewhere PHP 43 or something :D
>
> Seriously. From PHP x.y.z to PHP x.y.z+1
> tl;dr the PHP developers have a false belief in not breaking backwards
> compatibility in minor releases.

No, but there are way too many possibilities to break things without
us even noticing it.

That's why we proposed the release process and rules RFC:
http://wiki.php.net/rfc/releaseprocess which clearly disallow BC
breaks in bugs fixes releases. Given that we have a way to actually
test releases efficiently.

We constantly work to improve QA as well, it is also why I asked for
apps and frameworks authors or QA lead to get in touch to see how we
can have your tests valid our changes.

Cheers,
--
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org