Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75269 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 55999 invoked from network); 6 Jul 2014 00:23:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jul 2014 00:23:15 -0000 Authentication-Results: pb1.pair.com smtp.mail=kris.craig@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=kris.craig@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.54 as permitted sender) X-PHP-List-Original-Sender: kris.craig@gmail.com X-Host-Fingerprint: 209.85.219.54 mail-oa0-f54.google.com Received: from [209.85.219.54] ([209.85.219.54:56684] helo=mail-oa0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A6/63-30974-2F698B35 for ; Sat, 05 Jul 2014 20:23:15 -0400 Received: by mail-oa0-f54.google.com with SMTP id eb12so3041622oac.13 for ; Sat, 05 Jul 2014 17:23:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dAbEEray4rDRuWkbhf5vf8ZBLxPIltK/8HolBtUJEzE=; b=xjjZpwG5YVN1RoJnhJBVzgMj9C3P28gXKwGND9FX429tkUJdZpNBBqxLgxQcEEhRrc PlJo5bFMpG4YnrmKMH8YEEW6W1oWruscpmS0b9tIk5jMZ2USByTr3jq1iLmxRX7dTQWd 2LV4YX3QrAbl6JWf/g/W1VCG+Fw6AYNdzQWizYIlgDRKQ4JCsGiroZxVFB2RByVJ7eEw Y3V1keWUwGcHEE7nDTtYXUvawnnYwWin+LIwGwDRmtNaw9TQzsI1V8+j+tlSwvKYUetp OEzOklWBK0cfqnjuz3nNM9RtrOsMMxp5ks75yH6l8KpZGTNOLVw56pRIuUatF/Bt7OJx Ppzg== MIME-Version: 1.0 X-Received: by 10.182.224.163 with SMTP id rd3mr21534548obc.41.1404606191865; Sat, 05 Jul 2014 17:23:11 -0700 (PDT) Received: by 10.202.15.72 with HTTP; Sat, 5 Jul 2014 17:23:11 -0700 (PDT) In-Reply-To: References: <61EEC54E-7B8D-433E-A391-75F8D6A41E79@ajf.me> <650742796f119ed972a688a58e02242b@mail.gmail.com> Date: Sat, 5 Jul 2014 17:23:11 -0700 Message-ID: To: Andrea Faulds Cc: Zeev Suraski , PHP Content-Type: multipart/alternative; boundary=089e013a211c1d94b604fd7b5dab Subject: Re: [PHP-DEV] [RFC] Name of Next Release of PHP From: kris.craig@gmail.com (Kris Craig) --089e013a211c1d94b604fd7b5dab Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sat, Jul 5, 2014 at 4:18 PM, Andrea Faulds wrote: > > On 6 Jul 2014, at 00:05, Zeev Suraski wrote: > > > I think there's some confusion here. > > > > If the next version of PHP is going to be a major one (which is clearly > > defined in https://wiki.php.net/rfc/releaseprocess), then I believe the > > only two options that were ever raised are PHP 6 and PHP 7. If you're > > aware of other proposals that were made then please state them, > otherwise, > > I think it's a very clear decision between 6 and 7 - and putting this a= s > a > > 'yes/no' for 6 gives it undue advantage. > > Well, if we have the current yes/no to PHP 6 vote, then if it passes, we > get PHP 6. If it doesn=E2=80=99t pass, we=E2=80=99re back where we were b= efore. > > If we go for PHP 6/PHP 7 vote, then the result is unclear. Would one > option be the default? Would it be PHP 7 if it=E2=80=99s not PHP 6? Would= it be PHP > 6 if it=E2=80=99s not PHP 7? In which case, what=E2=80=99s the point in a= majority? We > could hold a 50%+1 vote, but such a vote would be contentious and would b= e > a popularity contest, not requiring consensus. If we don=E2=80=99t have a= default, > and either 6 has to get 2/3 or 7 has to get 2/3, then we should have an > Other option, or a Continue Discussion option, or both. This is all way t= oo > complicated for me and I don=E2=80=99t want the vote to be contentious or= confusing. > > Hence, it is a Yes/No vote to PHP 6. If it fails, we are back to where we > were before. If it passes, the name is PHP 6. It could not be more > straightforward, and the result cannot be misinterpreted. It requires a 2= /3 > majority to pass, so it would require consensus. Again, this is my positi= on > and I am sticking to it. I see no good reason to complicate matters. > I tend to agree. PHP 6 is the next increment. The question is whether we should continue following that standard or break from it for the reasons raised in the previous thread. If we break from it, then we'd have to decide what the next version name would be. However, based on the results of the previous thread on this matter, it seems extremely unlikely that the vote wouldn't be yes for PHP 6, so I don't think there's any pressing need to expand the scope of this vote beyond that. We should first establish whether or not we're sticking with the current conventions and going with PHP 6. If the vote is in favor of going another route, we can then put together a new RFC to figure out what the new convention should be (whether to arbitrarily skip a version increment or do away with the incremental number entirely and go with something else, like "PHP " or "PHP "). I certainly wouldn't agree that 7 is the only other option. Personally, my vote would be to keep the current naming convention and not skip 6. But if the outcome goes the other way, my preference would be to break from the incremental number system altogether because that'd be less confusing than an arbitrary skip, so it'd make more sense to be able to vote on that when and if people vote to discontinue the current naming convention and not go with the next increment of 6. --Kris --089e013a211c1d94b604fd7b5dab--