Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94327
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.220.169 cause and error)
MIME-Version: 1.0
In-Reply-To: <CAEZPtU7FB0GSYFq=8uiPQ76zas7S5eWxp1Xy69pwB8Md2hLkfQ@mail.gmail.com>
References: <A447792E-9DA6-4067-9EA5-7B6910520A8F@trowski.com> <CAEZPtU7FB0GSYFq=8uiPQ76zas7S5eWxp1Xy69pwB8Md2hLkfQ@mail.gmail.com>
Date: Wed, 29 Jun 2016 21:41:54 +0100
Message-ID: <CA+kxMuR71mgn-jfsj2fYXXQgOQ_CP8i3hdZEW0bP9-T8E9QDuQ@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Cc: Aaron Piotrowski <aaron@trowski.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC][Vote] Throw Error in Extensions
From: danack@basereality.com (Dan Ackroyd)

On 28 June 2016 at 03:36, Pierre Joye <pierre.php@gmail.com> wrote:
>
> I like the idea.
>
> It should be 2/3 tho'.

Why?

It's not a language change, so doesn't seem to meet the criteria for
needing a 2/3 pass rate.

For the record, I'm beginning to think the RFC process should probably
be slightly more orchestrated, and RFCs should have a "pre-vote"
announcement at least one week before the vote actually opens, when
the RFC author thinks the discussion of the RFC is complete.

This point would be the time for the implementations full impact on
the PHP engine to be analyzed, and also when the final voting choice
can be discussed/challenged before the voting is actually open.

cheers
Dan