Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99482
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.176 as permitted sender)
Date: Sat, 10 Jun 2017 20:29:04 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <4b3a548c-fd9f-42da-93c7-e8403f065da5@php.net>
References: <CAJd4=YaMDkocahDE0muQNPYW=vgR_nffJD-CBKic7CnbFPwyyw@mail.gmail.com> <eadc5bea-3412-9c9b-faa9-e74b442a6b84@gmx.de> <7028fcfd-d47f-c983-510d-eefe4a36cd4a@tekwire.net> <CAJd4=YadTb6wspVz7zAVh0wuasZdtCsjMnnER40y_ib3A5QVbw@mail.gmail.com> <4b3a548c-fd9f-42da-93c7-e8403f065da5@php.net>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: internals@lists.php.net
Message-ID: <71DDC799-25C8-4276-85BC-5CDC569E7788@gmail.com>
Subject: Re: [PHP-DEV] Re: [RFC] [VOTE] Arrays starting with a negative index
From: rowan.collins@gmail.com (Rowan Collins)

On 8 June 2017 08:52:41 BST, "Fran=C3=A7ois Laupretre" <francois@php=2Enet>=
 wrote:
> It would be great, IMO, to open a 'Approved for 8=2E0' section
>on=20
>the RFC page now, and your RFC could proudly be the 1st one to enter
>it=2E

I definitely agree with this, as I've argued before for a more timeline ba=
sed approach to major releases to avoid / reduce a repeat of the "quick, wh=
ile 7=2E0 is on the table" RFC rush, and the "well, 7=2E1 is still kinda th=
e beginning of 7=2Ex, so we can break things a little" kludges=2E

There is still the question of how to ease the transition, though: a subtl=
e break documented years in advance is still a subtle break, so we need to =
think what form of deprecation is useful to developers=2E That means more t=
han restarting voting with a new target version, and if the final target is=
 8=2E0, there's no rush to hold that new vote=2E

Regards,

--=20
Rowan Collins
[IMSoP]