Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84938 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81128 invoked from network); 15 Mar 2015 22:08:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Mar 2015 22:08:48 -0000 Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 74.125.82.52 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 74.125.82.52 mail-wg0-f52.google.com Received: from [74.125.82.52] ([74.125.82.52:35379] helo=mail-wg0-f52.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2D/A1-06614-DE206055 for ; Sun, 15 Mar 2015 17:08:46 -0500 Received: by wgdm6 with SMTP id m6so26229891wgd.2 for ; Sun, 15 Mar 2015 15:08:42 -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=H4ITF8klTzvzrCJzm5/oOC8uqKZZiB/wYk08NtvyuOQ=; b=a+3/qVp+fNT+VrdbPztMQp8FRap1cViKLQLU22xeJJl7er3wTfiMuhsurNjxv8IM5D gfmdFl8BnZGqVTuEWlm4mmqWajaJXRS07rXI7bn53NnnOqxTSOSKGrq/etd5wGCJQWEc xBLUL922Shn82fbpAkPjyC1ozpI20+0kyeosKbZdG8UU4zId/skiztnWUuTdbNvTCGMk qAIxmQpjp1t7LWlgI/6i3dS/iYZ0vq35OEeawaicG2eH9fVZOJiRD2pqubR1AiD0cDEv uxD33ayMbdatNszfzPmK0ty+E23SnhRlKqqu6FEDxNNRD6yUMdmvk7k6qbI5afilsMdl C9cg== X-Gm-Message-State: ALoCoQnKITvBlbUzcca4VD+BDw5hCOsi7crA3EvXm3PtocXt5MO0GyfiakCEwPcNZNZP5tZz8LurWX1hE4eN+xZW7WFNFT1jL4JIx/JhHdmt+aFjFJJm9BOOTvAQN6E6lwsiUvoPnvRmHldw+UBvyIU8aGM4VJm8Aw== X-Received: by 10.180.91.79 with SMTP id cc15mr145949806wib.37.1426457322411; Sun, 15 Mar 2015 15:08:42 -0700 (PDT) References: <6e268626bc6b84a3886f39442c827bb6@mail.gmail.com> <9cc36c9a8c15ba411a8f2981ff18678c@mail.gmail.com> <556399ae939b3e947381b1c50db2de6b@mail.gmail.com> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKV59C6R/g00R7Uu5aQCj/uhXIapAFVjcT/AZ4zTjMDUyhKxQLGYVwYAs7zePsCU4OIfgITWgqkAc8B+poB/HmqdQLPyKUwmtwHBBA= Date: Mon, 16 Mar 2015 00:08:41 +0200 Message-ID: <029b2f17a85e1bc03504d82772de1f26@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 11:12 PM > To: Zeev Suraski > Cc: PHP Internals > Subject: Re: [PHP-DEV] [RFC] [INFO] Basic Scalar Types > > > Are there some special rules for a backup > > plan anywhere in the Voting RFC or the Timeline RFC that I missed? > > Yeah Bob specifically said it would go to vote if Dual STH failed, so > that makes it a backup plan. :) You're answering an unknown question I didn't ask. I asked whether there was anything in the Voting RFC (wiki.php.net/rfc/voting) or the Timeline RFC (wiki.php.net/rfc/php7timeline), the two RFCs being used to block a Basic STH poll from going to a vote for PHP 7.0, that somehow make it legitimate for it to be proposed if the Dual Mode RFC fails. The answer - there's not. Zeev