Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94047
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.43 as permitted sender)
References: <6c03dafd-093a-0087-6312-96fede93c5f0@gmail.com>
 <BY2PR0201MB17843F26C4E02181DDDED285BF540@BY2PR0201MB1784.namprd02.prod.outlook.com>
 <1c437efe-7f1d-629f-cfbc-41cbcda38d89@fleshgrinder.com>
 <CAEZPtU6PonqQcT5sQf1FUd-Vwp-qcZ5r0jzL-Cdn3r3=wpLJDA@mail.gmail.com>
 <CAFMT4NoqmuA-LySitfMJS_2d4re5o75jw7FyqDuHWbZD1S6eLQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Message-ID: <b1ffc667-8b74-5be8-9945-f5ebee072045@gmail.com>
Date: Thu, 16 Jun 2016 17:30:54 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <CAFMT4NoqmuA-LySitfMJS_2d4re5o75jw7FyqDuHWbZD1S6eLQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Is the "No BC Breaks in Minor Releases" policy
 enforceable?
From: rowan.collins@gmail.com (Rowan Collins)

On 16/06/2016 17:24, Levi Morrison wrote:
>> I also have to say that to the very short timeline to finalize 7.0
>> should not be paid by breaking BCs in 7.x. We can have a short
>> timeline for 8.0 as well. If we need more drastic BC breaks earlier
>> than expected. If JIT is a goal for 8.0, then let do the BC breaks in
>> 8.0 and prepare our users using 7.x.
>
> I agree with sentiment. However I do not mind certain BC breaks being
> made in 7.1. For 7.2 and beyond I think we should be significantly
> more strict on BC breakages.

Why? What's special about 7.1? If it was a case of finishing off changes 
that "should have been part of 7.0", I can see some kind of logic, but 
the ones we're actually discussing seem to be more about "preparing for 
8.0".

Regards,
-- 
Rowan Collins
[IMSoP]