Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89713
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.50 as permitted sender)
To: internals@lists.php.net
References: <d7986bddhrs5d7o2c6r42g6h9to3au5kq0@4ax.com>
 <11.24.55814.5A495665@pb1.pair.com> <56659949.8080405@gmail.com>
Message-ID: <56659ABA.5010708@gmail.com>
Date: Mon, 7 Dec 2015 14:42:02 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <56659949.8080405@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: PHP 5.6 life cycle
From: rowan.collins@gmail.com (Rowan Collins)

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.