Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84901 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19481 invoked from network); 15 Mar 2015 20:23:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Mar 2015 20:23:25 -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:36716] helo=mail-we0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6F/B4-31306-A3AE5055 for ; Sun, 15 Mar 2015 15:23:24 -0500 Received: by wetk59 with SMTP id k59so25152884wet.3 for ; Sun, 15 Mar 2015 13:23:20 -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=PS5K+n8v06rYKddRzs0TxCkJb7oSVSF8bqVU9/ERzeU=; b=YBw+slBEar8S3w+wWOybIvHHW1MOwQxD/aNnvn9R+fCoKhZJhDOA71EW6NeR4PdPfy DYNwNnGFNiidpJcgKighOoUI3nx0ja//BzgzomBhvdsIsFff59/LWAf34mioKLk40qul obYWPuuQ4EfPZImAiejN3Zo3SstDflEXSyjxOWJrIKvOgxhrQQ55P99KLOf+IrMpFCx/ VIQOj13yYe+dEWOWgJ5eE5ebaa2300Cn8xnd/OKW2/pbLtOMxAlHdztD24yeg/DPyNVO sTPwkq9Q0dv14Z6wtG63MFuqgAks8ST6H1FBQl3Q+w/7BEaEtoikiWMb4PpIzxg0Y12Y MiNg== X-Gm-Message-State: ALoCoQlO3IgmUb7j9vrhGRBG+o/kURNdcENkPkhXEl5RvnwV+MovJZggT2WKNlUgQfj4enk8GZUtA2Snu+sSprbyiWbsmfPkia35y+HzKxg8+kNFLfpYtxCsOMTlC/E+GnOvpnU28vvhFiB1goK6mnxUfO8n2xFWeg== X-Received: by 10.180.207.200 with SMTP id ly8mr32316230wic.58.1426451000201; Sun, 15 Mar 2015 13:23:20 -0700 (PDT) References: <6e268626bc6b84a3886f39442c827bb6@mail.gmail.com> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKV59C6R/g00R7Uu5aQCj/uhXIapAFVjcT/AZ4zTjMDUyhKxQLGYVwYAs7zePsCU4OIfpshaXoQ Date: Sun, 15 Mar 2015 22:23:19 +0200 Message-ID: <9cc36c9a8c15ba411a8f2981ff18678c@mail.gmail.com> To: Nikita Popov 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) > 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