Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76099 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45562 invoked from network); 25 Jul 2014 08:28:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jul 2014 08:28:32 -0000 Authentication-Results: pb1.pair.com smtp.mail=phoenix@jonstirling.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=phoenix@jonstirling.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain jonstirling.co.uk from 209.85.217.174 cause and error) X-PHP-List-Original-Sender: phoenix@jonstirling.co.uk X-Host-Fingerprint: 209.85.217.174 mail-lb0-f174.google.com Received: from [209.85.217.174] ([209.85.217.174:50610] helo=mail-lb0-f174.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BF/88-29475-F2512D35 for ; Fri, 25 Jul 2014 04:28:32 -0400 Received: by mail-lb0-f174.google.com with SMTP id c11so3170962lbj.33 for ; Fri, 25 Jul 2014 01:28:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=18ENdWrhhFEcxyCqBXnuMyiw93XgQqy9xTmb/9aNoTc=; b=mwpa2b+GsYM1WfZ7/v3jr4S76zVSN4L6Df9PWAxnf3YrUFwR4TgPY1cTcoZ2rUD9tS 7IcPwG4IIlrIDUcy9n3dJDnWjxFuZYneg0E2C3I33kFYm76qvdz6+2NC4l78FTVc/9M3 AVCjsLxdjKPXoBB4mHMmlkZtHBvJsalXLVCmS1sum3X71Fu2bQilNFqqPV98Dg+1BMv0 pkdCYRAYVTrz4kGDpTjDcz6geO1dJ3JVFPcvPrjP1XzJ6JNnKGaLxo/bWDxwcdqkNwkB n6CZcujBXQtrubukXylP58hQDdlzVvCGfd3nM9P4bt9OieW1SgyNsaDCQtCMY6WIFVlY ADVA== X-Gm-Message-State: ALoCoQm6PA9dIPnHb0xafdfn2n9jxSTS3Bg5LmC7KREg4TTg+j0DKUxApKfNXojelDjAf8wEp8cB MIME-Version: 1.0 X-Received: by 10.112.19.133 with SMTP id f5mr13551467lbe.48.1406276914033; Fri, 25 Jul 2014 01:28:34 -0700 (PDT) Received: by 10.152.132.227 with HTTP; Fri, 25 Jul 2014 01:28:33 -0700 (PDT) X-Originating-IP: [62.252.0.138] In-Reply-To: References: Date: Fri, 25 Jul 2014 09:28:33 +0100 Message-ID: To: Zeev Suraski Cc: Dmitry Stogov , Yasuo Ohgaki , PHP internals Content-Type: multipart/alternative; boundary=14dae93d8c86ead17404ff005bd7 Subject: Re: [PHP-DEV] RFC: Move phpng to master From: phoenix@jonstirling.co.uk (Jonny Stirling) --14dae93d8c86ead17404ff005bd7 Content-Type: text/plain; charset=UTF-8 Hi Zeev, Now we're into arguing semantics of the Voting RFC. Whether you meant something else when you wrote that is now irrelevant, it's what is written that is the rule, not somebodies individual interpretation surely? "In any meaning full way" are your words, not what the accepted RFC states. From what's been said previously, the changes in NG are strictly implementation changes, i.e. syntax etc remains the same throughout. That's great, and would require a 50%+1 for vote as far as I can see. However. If there are /any/ changes to what end-users would see, that is by definition a change in the language, no matter how small (or "meaningless"), you are into 2/3 majority territory. So, can those who have worked on it confirm with a simple yes / no, are there changes (right now) that may affect users. Second, if the answer is "no", is there somebody that can review and confirm that this is the case that hasn't worked on NG preferably (not because of trust, just because it's a large changeset which makes it easy to miss stuff and a fresh pair of eyes is good). Now. If yes, 2/3 majority is required. It's as simple as that. If no, then I would suggest starting the review to confirm. I would hope that the remaining time in the 2 weeks would be enough to accomplish a review, but somebody correct me if they think otherwise, so the vote start / end should hopefully be unaffected beyond vote requirements. Cheers. Jonny. --14dae93d8c86ead17404ff005bd7--