Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90598 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 9050 invoked from network); 13 Jan 2016 13:16:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Jan 2016 13:16:22 -0000 Authentication-Results: pb1.pair.com smtp.mail=bobwei9@hotmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=bobwei9@hotmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain hotmail.com designates 65.55.111.173 as permitted sender) X-PHP-List-Original-Sender: bobwei9@hotmail.com X-Host-Fingerprint: 65.55.111.173 blu004-omc4s34.hotmail.com Received: from [65.55.111.173] ([65.55.111.173:62421] helo=BLU004-OMC4S34.hotmail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0F/E3-13057-52E46965 for ; Wed, 13 Jan 2016 08:16:21 -0500 Received: from BLU436-SMTP148 ([65.55.111.135]) by BLU004-OMC4S34.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Wed, 13 Jan 2016 05:16:18 -0800 X-TMN: [gqBG8uzaeoM0NKeIFJlBjzDJ2kArW6VR] X-Originating-Email: [bobwei9@hotmail.com] Message-ID: Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) In-Reply-To: Date: Wed, 13 Jan 2016 14:16:13 +0100 CC: Joe Watkins , PHP internals Content-Transfer-Encoding: quoted-printable References: <373698cabe053cb9bec8e1f6dc969906@mail.gmail.com> To: Zeev Suraski X-Mailer: Apple Mail (2.3096.5) X-OriginalArrivalTime: 13 Jan 2016 13:16:15.0783 (UTC) FILETIME=[950B3370:01D14E04] Subject: Re: [PHP-DEV] [RFC] [VOTE] PHP 5's Support Timeline From: bobwei9@hotmail.com (Bob Weinand) 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 > Am 13.01.2016 um 14:02 schrieb Joe Watkins : >=20 > The no votes should be counted as votes for option one schedule. >=20 > Which makes the vote a tie, and if any changes are going to be made, = we > should be using option 1 schedule, not 2 ... >=20 > Cheers > Joe >=20 > On Wed, Jan 13, 2016 at 11:51 AM, Zeev Suraski wrote: >=20 >> All, >>=20 >> The vote has been closed. It was approved 42 to 2 (95.5% in favor). >> There was a close race between the two available extended schedules, = and >> the one selected is Active Support until December 31st 2016, and = Security >> Support until December 31st 2018. >>=20 >> Thanks to everyone who participated & voted! >>=20 >> Zeev >>=20 >> From: Zeev Suraski >> Sent: Tuesday, January 05, 2016 11:52 AM >> To: PHP internals >> Subject: [RFC] [VOTE] PHP 5's Support Timeline >>=20 >> Hopefully mostly everyone is back from the holidays by now, the vote = is >> now open for the PHP 5 Support Timeline RFC: >>=20 >> https://wiki.php.net/rfc/php56timeline#vote >>=20 >> Voting ends January 13th 2016 at 10:00am GMT. >>=20 >> Thanks! >>=20 >> Zeev