Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93973
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.175 as permitted sender)
To: internals@lists.php.net, Dmitry Stogov <dmitry@zend.com>,
 Rowan Collins <rowan.collins@gmail.com>
References: <6c03dafd-093a-0087-6312-96fede93c5f0@gmail.com>
 <BY2PR0201MB17843F26C4E02181DDDED285BF540@BY2PR0201MB1784.namprd02.prod.outlook.com>
 <1c437efe-7f1d-629f-cfbc-41cbcda38d89@fleshgrinder.com>
Message-ID: <155a8c29-7858-74a6-7c45-5746d79e9a72@gmail.com>
Date: Tue, 14 Jun 2016 12:43:30 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0)
 Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <1c437efe-7f1d-629f-cfbc-41cbcda38d89@fleshgrinder.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Is the "No BC Breaks in Minor Releases" policy
 enforceable?
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> Isn't that just an excuse to creep in breaking changes? We all
> understand the goal here and we all are in favor of it. The problem is
> that it still is a breaking change. It would be better to elevate the
> E_INFO to an E_WARNING and create that PHP-8.0 branch with the actual
> error and start planning the 8.0 release.

Changing notice to warning is a breaking change too :) And I'm not sure
how rushing 8.0 helps anything if you're afraid of breaks - you get
useful features later but also bigger breaks. Long term it doesn't
matter anyway unless 7.1 is somehow special, which is not. Also, having
just two minor versions seems to be a little thin, unless there's a plan
to keep maintaining 7.x, in which case the question is - who's going to
do that?

-- 
Stas Malyshev
smalyshev@gmail.com