Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75270
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAKOpQSyJCDwJUqh4OuWd9YnDjcFMj3XqafJbOLM-uV_ipoM5XA@mail.gmail.com>
References: <61EEC54E-7B8D-433E-A391-75F8D6A41E79@ajf.me>
	<650742796f119ed972a688a58e02242b@mail.gmail.com>
	<CA0E4289-C03E-48E0-ACA3-FB9CD9632FBD@ajf.me>
	<d551b5cd173fde7b3192f9fb740fc4e5@mail.gmail.com>
	<E0A23B54-C1E5-446A-AB97-3A90A336EC0D@ajf.me>
	<CAKOpQSyJCDwJUqh4OuWd9YnDjcFMj3XqafJbOLM-uV_ipoM5XA@mail.gmail.com>
Date: Sat, 5 Jul 2014 17:29:08 -0700
Message-ID: <CAKOpQSwgqJxvh75cn-jO22okztrFOVyT3JPe+gP6ef-iCHe-tg@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Zeev Suraski <zeev@zend.com>, PHP <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0158ac86626f9204fd7b7226
Subject: Re: [PHP-DEV] [RFC] Name of Next Release of PHP
From: kris.craig@gmail.com (Kris Craig)

--089e0158ac86626f9204fd7b7226
Content-Type: text/plain; charset=UTF-8

I would, however, recommend that Andrea take Zeev's input and create a more
comprehensive section outlining his arguments in favor of breaking from the
current convention.  Another section could be created to outline the other
side.  What we don't want is a situation where Zeev feels compelled to
write a competing RFC.  That could get messy, so I think it'd be best if
the two of you could find enough common ground to make this RFC acceptable
to both sides.

I'd also recommend that, since you're calling for a 2/3 vote, you specify
more clearly what it is that requires 2/3; breaking the current convention
or keeping the current convention?  I'm guessing you probably meant the
former, but the wording seemed a bit vague on that point to me.

--Kris

--089e0158ac86626f9204fd7b7226--