Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90622 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 55919 invoked from network); 13 Jan 2016 17:24:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Jan 2016 17:24:38 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.171 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.214.171 mail-ob0-f171.google.com Received: from [209.85.214.171] ([209.85.214.171:34080] helo=mail-ob0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 22/24-34116-45886965 for ; Wed, 13 Jan 2016 12:24:36 -0500 Received: by mail-ob0-f171.google.com with SMTP id vt7so60810738obb.1 for ; Wed, 13 Jan 2016 09:24:36 -0800 (PST) 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=wVs64eZi30W0kFGbJ90Ui6n8JCKJWQ9vIJOfp+fprPQ=; b=R/I54QaaEyHxr0f6axnR2c++x4ktZRu9vY0CkpewFUdi34as+5gMCanEnmBx0KT5/v 0yVeC0H7aMhA7MsWscexmDZiX/zLldRjdr22ccNZhchLicKrlxufRAWh1u9a2Y2zhj64 tYFPsxAU7sLMeHcDi6bciTW0X7B0ZnQDow+44E227jeNS6f+TT5FEywBzBuPvhLQK6Jt SVZb8XiGzUvC3eS0QnBjRMD3a7EeZPLVYe/WuAbkFzdBhNdf2Jnn1qVIr9JNpH+MACWs aT3RERUA35fB9VmFCtctiw8op/A0C5BF9P/GXG4FdYJJbZXiyvVH6AB+B9C6Lu8YjS7q gtzw== 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=wVs64eZi30W0kFGbJ90Ui6n8JCKJWQ9vIJOfp+fprPQ=; b=ZtGGkuUrQA69k5XW4e+K+lNFa1iiJgyxLi890RaowhexKyTDOx0vmvhD+MPhtBZROM F+a25Qvsc2l01DpjYMxFAbzhyFVy7kXZiDxL3PCyUpJKXwDHeih82kF69ZKupsCKHqtj xcjUz1ehlW4Ea6p8/FAd/1toPCKQmvxxzk5lb4XdY44NPLJ/2NOCADsaQb1+/wDfNLgL xovYgt4MhmOHic4661NcXx6ubpKsdG/Sx3w6kp9O7jeLRbPEdnUrUISdsgvivVg+2aYf lQI9f0iyWlagdRAu6Y2mtDSYuW6H0vZ3p63jewQaSHPxYLh3lBcjPsOPU+ISAKjgN1ts oVAQ== X-Gm-Message-State: ALoCoQkE4DEXQRyLB+b5NmTQ8zOCWd5y8hUVR510SiHvUsFziQPq5KmiDTawI4/pKxoyk8BiNLTwhDM3tzvsJNKznEWSaHPLxg== MIME-Version: 1.0 X-Received: by 10.60.63.81 with SMTP id e17mr42898754oes.21.1452705873648; Wed, 13 Jan 2016 09:24:33 -0800 (PST) Received: by 10.202.95.68 with HTTP; Wed, 13 Jan 2016 09:24:33 -0800 (PST) Received: by 10.202.95.68 with HTTP; Wed, 13 Jan 2016 09:24:33 -0800 (PST) In-Reply-To: References: <373698cabe053cb9bec8e1f6dc969906@mail.gmail.com> Date: Thu, 14 Jan 2016 00:24:33 +0700 Message-ID: To: Joe Watkins Cc: Bob Weinand , PHP internals , Zeev Suraski Content-Type: multipart/alternative; boundary=001a11c256b68fe3a605293a7109 Subject: Re: [PHP-DEV] [RFC] [VOTE] PHP 5's Support Timeline From: pierre.php@gmail.com (Pierre Joye) --001a11c256b68fe3a605293a7109 Content-Type: text/plain; charset=UTF-8 On Jan 13, 2016 10:42 PM, "Joe Watkins" wrote: > > > The way the RFC the choices are going to be interpreted was presented > ahead of time, was available throughout the entire discussion period, and > very clearly so: > > So what !? > > The terms are clearly biased towards the longest support period if "no, I > don't want to extend support period" is going to be taken to mean "yes, > extend the support period using the longest option" ... > > Whatever, the options don't make sense ... Why I change my vote from no to extend to yes and take the shorter options. It would have been better to have all options clearly exposed. > Cheers > Joe > > On Wed, Jan 13, 2016 at 2:05 PM, Zeev Suraski wrote: > > > > -----Original Message----- > > > From: Bob Weinand [mailto:bobwei9@hotmail.com] > > > Sent: Wednesday, January 13, 2016 3:16 PM > > > To: Zeev Suraski > > > Cc: Joe Watkins ; PHP internals > > > > > > Subject: Re: [PHP-DEV] [RFC] [VOTE] PHP 5's Support Timeline > > > > > > I agree, > > > > > > no votes should be meaning "I want as less as possible support". > > > Counting it that way would make it up for a tie and us choosing the most > > > restrictive schedule as a result. > > > (Interpreting it like "you need 50%+1 of the total to get it extended so > > far".) > > > > > > Hence Security Support until Dec 31 2017. > > > > Bob, > > > > The way the RFC the choices are going to be interpreted was presented > > ahead of time, was available throughout the entire discussion period, and > > very clearly so: > > "In case the majority chooses to extend the lifetime of PHP 5.6 (>50%) - > > then the option garnering more votes between the two proposed timelines > > would win." > > > > I'm not sure what the situation would have been had we truly had a 23/23 > > split, probably a revote or an extended voting period, but the current > > situation is very well defined under the RFC terms. > > > > Thanks, > > > > Zeev > > > > > > -- > > PHP Internals - PHP Runtime Development Mailing List > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > --001a11c256b68fe3a605293a7109--