Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84909 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32836 invoked from network); 15 Mar 2015 20:45:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Mar 2015 20:45:01 -0000 Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 74.125.82.171 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 74.125.82.171 mail-we0-f171.google.com Received: from [74.125.82.171] ([74.125.82.171:34022] helo=mail-we0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F2/87-31306-B4FE5055 for ; Sun, 15 Mar 2015 15:45:00 -0500 Received: by wegp1 with SMTP id p1so25333475weg.1 for ; Sun, 15 Mar 2015 13:44:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=fo8ax4gjr04HhU5fPejZjsHZ8fwMzW9UW1+YL/fjPYQ=; b=aF81792BUy/pc0fr4Ww4xozC8a5l+LZfQUPDapKdtZnPWuxvmFO0gZrzFDzvoT4g2c h85e9XBhAyJ2k8uPV+ZMpaIBhW26kEBGjFhuJ6z50/r/k0iKqEQMqh9cxc+gVk6hDKir 7UJwXYPqb/4D8rbm9P7OdtH5h5XXjTjk/FvwEX68h7hzKoTJ30FF4WnxE9asaq9LP+Av ywZYDg1RCx7lCwroS/z93Cc0dC5ycU/XTAW9EGdOlgJrVgrhtLilF1Wv1Gk29tSIlcHP pMxrsJoKQvxUWlWrOR/tYPsRJcsw53sFWVxJIz8qJTatT0CXmKawct34Sbg9wXFZNS32 uLqA== X-Gm-Message-State: ALoCoQnr6+hW7BZfS8S/tOwUz9X7ljlJSqTeHqhx4KBvmedfyB9KhmzgmGREy09iKO87gYbECqbPoLdq918MxZoQNlIKFPk2RLLJGWwTe6fVv2Lzb1ElV6WBjZsoP8n+vUyBGh/dlRIyF+2Z7QAZMhU3vIJHekK2bw== X-Received: by 10.194.177.132 with SMTP id cq4mr111525165wjc.99.1426452296170; Sun, 15 Mar 2015 13:44:56 -0700 (PDT) References: <6e268626bc6b84a3886f39442c827bb6@mail.gmail.com> <9cc36c9a8c15ba411a8f2981ff18678c@mail.gmail.com> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKV59C6R/g00R7Uu5aQCj/uhXIapAFVjcT/AZ4zTjMDUyhKxQLGYVwYAs7zePsCU4OIfgITWgqkAc8B+pqbAl9xMA== Date: Sun, 15 Mar 2015 22:44:55 +0200 Message-ID: <556399ae939b3e947381b1c50db2de6b@mail.gmail.com> To: Philip Sturgeon Cc: PHP Internals Content-Type: text/plain; charset=UTF-8 Subject: RE: [PHP-DEV] [RFC] [INFO] Basic Scalar Types From: zeev@zend.com (Zeev Suraski) > -----Original Message----- > From: Philip Sturgeon [mailto:pjsturgeon@gmail.com] > Sent: Sunday, March 15, 2015 10:33 PM > To: Zeev Suraski > Cc: Nikita Popov; PHP Internals > Subject: Re: [PHP-DEV] [RFC] [INFO] Basic Scalar Types > > On Sun, Mar 15, 2015 at 4:23 PM, Zeev Suraski wrote: > >> Sorry, but ... even though your original RFC was very unclear about > >> this, everybody went by the "all votes must start by the 15th" > >> interpretation that has been discussed in that thread. Do you think > >> it's an accident that a whopping six RFC votes started today? It > >> isn't. > >> > >> > >> Please don't start reinterpreting things to fit your needs. I am > >> personally totally fine with extending the PHP 7 timeline by say one > >> month - but if we do that, let's make it official and applying to > >> everyone, not just some particular RFC. I know for sure that there > >> are a number of additional RFCs that would have been submitted for > >> PHP 7 had anyone known that it'll be allowed. > > > > First off, this is Bob's interpretation which he brought up on Friday. > > Yes, ideally I would have read the original text during the discussion > > period and commented on it, but I didn't. I think the 3 month period > > for implementation (that's mostly done) and testing gives a very > > reasonable time period to absorb the most lax of interpretations. > > > > I think it would be a shame to delay the timeline for this, but I also > > think it would be a shame for the timeline - that was *clearly* not > > designed to create de-facto bias towards one RFC or the other - to do > exactly that. > > > > Even if we were to push the timeline out by a bit, how do we do it? > > An RFC with a minimum discussion period of two weeks and another week > for a vote? > > That kind of defeats the purpose. A gentlemen's agreement? Something > else? > > > > Zeev > > > > -- > > PHP Internals - PHP Runtime Development Mailing List To unsubscribe, > > visit: http://www.php.net/unsub.php > > > > "Even if we were to push the timeline out by a bit, how do we do it?" > > This is ~"My approach hasn't won yet, and instead of conceding default due > to democracy in action, I would like to change the process. > > I am not insulting you. I am not attacking you. But this is some bizarre > stuff > that is more than sneaky, and you really need to stop. Phil, Do you mind STOPPING TO TWIST THINGS TO FIT YOUR AGENDA, please? And no, saying you don't insult me or attack me after doing exactly that does not change anything. It's NIKITA that proposed this. It's BOB that proposed the lax (and very reasonable) interpretation to the Mar 15 timeline. Why did you not 'not insult' and 'not attack' them? Is it open season on Zeev only? > One RFC has won. Another RFC has lost. A third RFC is a backup plan and > nothing more. None won and none lost as of yet. Are there some special rules for a backup plan anywhere in the Voting RFC or the Timeline RFC that I missed? Or are you allowed to make those up? How sneaky of you. And bizarre. But no worries, I'm not insulting or attacking you! *THIS* is toxic. If Nikita brings up a point, I ask him to elaborate a bit, and you jump on me (as you did numerous times over the last month) - this is unacceptable. Zeev