Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90604
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 157.56.110.103 as permitted sender)
To: Bob Weinand <bobwei9@hotmail.com>
CC: PHP internals <internals@lists.php.net>
Thread-Topic: [PHP-DEV] [RFC] [VOTE] PHP 5's Support Timeline
Thread-Index: AQHRTgSYahy/6BieGE2uZPURCL9KqJ75ePxg
Date: Wed, 13 Jan 2016 14:05:43 +0000
Message-ID: <BY2PR02MB29887B1092A73C5458ACE0FACCB0@BY2PR02MB298.namprd02.prod.outlook.com>
References: <373698cabe053cb9bec8e1f6dc969906@mail.gmail.com>
 <BY2PR02MB298CD3F862A71149FB29857ACCB0@BY2PR02MB298.namprd02.prod.outlook.com>
 <CAL=_i_mR9ue7W_=zZX19Zm3XY1kPaJfoho2U3ZdExNPXWQwN8Q@mail.gmail.com>
 <BLU436-SMTP1486256AA36AFDB5A00EDABE2CB0@phx.gbl>
In-Reply-To: <BLU436-SMTP1486256AA36AFDB5A00EDABE2CB0@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: zend.com does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jan 2016 14:05:43.4259
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 32210298-c08b-4829-8097-6b12c025a892
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR02MB300
Subject: RE: [PHP-DEV] [RFC] [VOTE] PHP 5's Support Timeline
From: zeev@zend.com (Zeev Suraski)

> -----Original Message-----
> From: Bob Weinand [mailto:bobwei9@hotmail.com]
> Sent: Wednesday, January 13, 2016 3:16 PM
> To: Zeev Suraski <zeev@zend.com>
> Cc: Joe Watkins <pthreads@pthreads.org>; PHP internals
> <internals@lists.php.net>
> Subject: Re: [PHP-DEV] [RFC] [VOTE] PHP 5's Support Timeline
>=20
> I agree,
>=20
> 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".)
>=20
> 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 c=
learly so:
"In case the majority chooses to extend the lifetime of PHP 5.6 (>50%) - th=
en 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 sp=
lit, probably a revote or an extended voting period, but the current situat=
ion is very well defined under the RFC terms.

Thanks,
=20
Zeev