Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85392
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.214.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAPwsocFSxCkizDjf4RKwJn4jvNjdHjoDqUsu=78hAcquEqddTg@mail.gmail.com>
References: <CAPwsocFSxCkizDjf4RKwJn4jvNjdHjoDqUsu=78hAcquEqddTg@mail.gmail.com>
Date: Sun, 22 Mar 2015 08:45:01 +0200
Message-ID: <CAPJnDK19pr4CdtupUpuhHZUquXRd+rtkrNcaDJX2JVRsmEcCKw@mail.gmail.com>
To: Leigh <leight@gmail.com>
Cc: PHP internals list <internals@lists.php.net>, tyrael@php.net
Content-Type: multipart/alternative; boundary=001a11c2ea348adbce0511dae380
Subject: Re: [PHP-DEV] 7.0 Release Management
From: lior.k@zend.com (Lior Kaplan)

--001a11c2ea348adbce0511dae380
Content-Type: text/plain; charset=UTF-8

On Sun, Mar 22, 2015 at 3:38 AM, Leigh <leight@gmail.com> wrote:

> Hi all,
>
> With 7.0 feature freeze in effect, and proposals and RFCs still coming in
> that are going to target 7.1, I think it's time we branched master and
> selected a release manager (or two) for 7.0.
>

I would branch only in time for the first beta... Similar to what
LibreOffice do:
https://wiki.documentfoundation.org/ReleasePlan/4.5#4.5.0_release

Rushing to push more features for 7.1 will come a t a cost of testing /
stabilizing 7.0.
It should be fine to ask people to delay feature suggestions for a little
later.

Kaplan

--001a11c2ea348adbce0511dae380--