Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80300
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain beccati.com designates 176.9.114.167 as permitted sender)
Message-ID: <54AFAAA5.4090301@beccati.com>
Date: Fri, 09 Jan 2015 11:17:09 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Internals <internals@lists.php.net>
CC: Andrea Faulds <ajf@ajf.me>
References: <14F63BD9-73FD-49A3-9EA2-48FE35DB915C@ajf.me>
In-Reply-To: <14F63BD9-73FD-49A3-9EA2-48FE35DB915C@ajf.me>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RESULT] [RFC] PHP 5.7
From: php@beccati.com (Matteo Beccati)

Hi,

On 08/01/2015 21:28, Andrea Faulds wrote:
> The vote on the PHP 5.7 RFC has closed. By 19 votes to 14, the RFC
> has been rejected. This means we won’t be having a PHP 5.7 release,
> unless another RFC is made and voted on.

I am still convinced that it was premature to open the voting on the 5.7
RFC.

The current PHP7 doesn't have huge BC breaks as far as I can tell, and
that's why I (and possibly others) have voted "no".

As of now, PHP 5.7 would have been for me just one more PHP version to 
take into account for CI/QA/testing. A burden if you will.

This might however change in the future, depending on the results
of forthcoming RFCs. If some "evil" BC breaks get to PHP7, then having 
5.7 might have been handy, but we've just ruled out this possibility.

Still, I just didn't feel it was right to vote "yes" based on such 
uncertainty.


Cheers
-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/