Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86311
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.179 as permitted sender)
User-Agent: K-9 Mail for Android
In-Reply-To: <CAFMT4No9C8-vv+6S8Dp+9tVyVV4wHF9BAPGjTbhH1hFOLLi1_w@mail.gmail.com>
References: <CAFMT4Np4N9gEcCLJ34dnCRnXwtVEyD5Xu6fpjXpdzpdfteEaFA@mail.gmail.com> <CAFMT4No9C8-vv+6S8Dp+9tVyVV4wHF9BAPGjTbhH1hFOLLi1_w@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
 charset=UTF-8
Date: Tue, 19 May 2015 18:49:44 +0100
To: internals <internals@lists.php.net>
Message-ID: <0AB88912-AAF8-4D96-9CB7-CB615AEBC9AE@gmail.com>
Subject: Re: [PHP-DEV] Soft-reserve "void" class name
From: rowan.collins@gmail.com (Rowan Collins)

On 19 May 2015 17:21:58 BST, Levi Morrison <levim@php.net> wrote:
>On a related note it is unclear what BC breaks are exactly allowed in
>minor releases. Adding new reserved types is a BC break, but it was
>done in PHP 5.4 with `callable`. We should solidify what we do and do
>not allow in minor releases for the PHP 7 release series.

5.4 is the wrong example to look at for BC precedent. It was immediately *after* 5.4's large number of changes (which were largely refugees from the sinking of 6.0) that a policy was adopted, and followed for 5.5, 5.6, and 7.0.

It still leaves some room for controversial interpretation, but it certainly disallows many of the things that happened in 5.4 outside of a major release, and this is by design.

https://wiki.php.net/rfc/releaseprocess

Regards,
-- 
Rowan Collins
[IMSoP]