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 <pthre...@pthreads.org>: > > The no votes should be counted as votes for option one schedule. > > Which makes the vote a tie, and if any changes are going to be made, we > should be using option 1 schedule, not 2 ... > > Cheers > Joe > > On Wed, Jan 13, 2016 at 11:51 AM, Zeev Suraski <z...@zend.com> wrote: > >> All, >> >> 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. >> >> Thanks to everyone who participated & voted! >> >> Zeev >> >> From: Zeev Suraski >> Sent: Tuesday, January 05, 2016 11:52 AM >> To: PHP internals <internals@lists.php.net> >> Subject: [RFC] [VOTE] PHP 5's Support Timeline >> >> Hopefully mostly everyone is back from the holidays by now, the vote is >> now open for the PHP 5 Support Timeline RFC: >> >> https://wiki.php.net/rfc/php56timeline#vote >> >> Voting ends January 13th 2016 at 10:00am GMT. >> >> Thanks! >> >> Zeev -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
