Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89716
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.213.49 as permitted sender)
References: <d7986bddhrs5d7o2c6r42g6h9to3au5kq0@4ax.com> <11.24.55814.5A495665@pb1.pair.com>
 <56659949.8080405@gmail.com> <56659ABA.5010708@gmail.com>
In-Reply-To: <56659ABA.5010708@gmail.com>
MIME-Version: 1.0
Thread-Index: AQHgh9Y9UJHbSHpdKU+NswaLC82f2wJyZEBEAow+Y9wC2qad4p5iKIzQ
Date: Mon, 7 Dec 2015 17:11:14 +0200
Message-ID: <2972914fdd1182ecf20d4c1cbd9b2c55@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>, internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Subject: RE: [PHP-DEV] Re: PHP 5.6 life cycle
From: zeev@zend.com (Zeev Suraski)

> -----Original Message-----
> From: Rowan Collins [mailto:rowan.collins@gmail.com]
> Sent: Monday, December 07, 2015 4:42 PM
> To: internals@lists.php.net
> Subject: Re: [PHP-DEV] Re: PHP 5.6 life cycle
>
> Rowan Collins wrote on 07/12/2015 14:35:
> > - On what factors will the decision be based? If the reason to delay
> > the decision is lack of information, what information are we planning
> > to use? Are there metrics we can use to make a more objective
decision?
>
> Come to think, this works the other way as well: if we *do* make a
decision
> now, are there factors that would allow the question to be reopened?
Again,
> to have any trust in the announced date, people would need to know what
> these were - if the decision is "probably August 2017", then that would
be no
> decision at all.

It's always possible to submit another RFC to alter the end date, even if
we decide about one now.  But I do think it'll send a different message -
that we think it's going to take extraordinary circumstances  for us to
change the decision - vs. us saying "we'll wait and see", which at least I
would interpret as "they'll probably delay it".

Zeev