Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79615
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.181 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <30315309863fc1883f187e2f6777d081@mail.gmail.com>
References: <CAMUwpuRZRb3z+gkU1ejctvfHGc_K=zWxSYmQn=TxVX9zS+fD0A@mail.gmail.com>
	<30315309863fc1883f187e2f6777d081@mail.gmail.com>
Date: Fri, 12 Dec 2014 12:59:44 -0700
Message-ID: <CAFMT4Npp+JpKvyJ5L75_w9rFipwdbtRNmBX4sdtT8jUo2G2bew@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: Julien Pauli <jpauli@php.net>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] On the road to PHP 5.7 , or not ?
From: levim@php.net (Levi Morrison)

>> - If we go for 5.7 :
>> We could release it this summer (2015) , but that would mean that 7.0
>> wouldn't come before summer 2016.
>> Releasing a 5.7 will lean the release cycle curve, but it is not
>> mandatory, that
>> should be debatted.
>
> A 5.7 that pushes 7.0 into Summer 2016 is IMHO a strategic mistake, but
> regardless I think the discussion is moot.  We've already decided we're
> aiming for a 2015 PHP 7.0 release, and should stick to that plan.

Assuming we do a PHP 5.7 as I outlined previously, it shouldn't take
anything more than a few hours here and there by a release manager and
a tiny bit of extra work for a few RFC authors. It's just normal bug
fixes, version bump, and compatibility stuff for PHP 7. As long as we
keep features out of PHP 5.7 it should not delay a PHP 7 release.