Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62905
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <slrnk4mc5m.g88.dsp@experimentalworks.net>
References: <slrnk4mc5m.g88.dsp@experimentalworks.net>
Date: Sat, 8 Sep 2012 16:15:43 +0200
Message-ID: <CAEZPtU4+gv_07OgskzbUn4YRS_qW9XUmzj766VHHR3iKMwYQxg@mail.gmail.com>
To: David Soria Parra <dsp@php.net>, internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Moving forward: PHP 5.5
From: pierre.php@gmail.com (Pierre Joye)

Hi!


On Sep 8, 2012 1:49 PM, "David Soria Parra" <dsp@php.net> wrote:

> As most people know we do not include patches in 5.4 that will break
> backwards compatibility.

We do not include them anywhere in any future 5.x release either.
That's clearly define in the RFC and we won't change that. Feedbacks
from users on that is clear and loud, best decision ever.

> Those patches are in the 5.5 branch and we
> are also stockpiling some new features.

There is o 5.5 branch, there is master. Master is the development
branch and as such can have such breakages. It does not mean that we
have these BC breaks in 5.5. 5.5 should be based on 5.4 with the
feature additions and improvements we want in, but definitively not
with BC breaks.

>  We have implementations for
> foreachlist, generators, hash_pbkdf2 and others are likely to get included
> in the next weeks like the simplified password hashing API.
>
> Following the release process RFC, I would like to start discussing the
> beginning of the 5.5. series, that can include new features, do bc breaks
> if necessary and overall provide a smooth move to a new series without
> having the branches diverge for years and years again (like 5.4 and 5.3).
> Last but not least, 5.3 is out since 2009 and it would be good to put
> the series into a security fix only mode and give it an eol.

Yes, let start the 5.3 EOL discussion too and decide when it will
stop, or better said, end the discussion as we began it earlier this
year :)

> As with every new release minor release (read minor as the Y in 5.Y.Z),
> we choose a new RM. We had quite some confusion and debates around this
> topic the last time, so I'll just go ahead and propose somebody right
> away for the job.

Two persons, actually.

> I would like to go ahead and propose Julien Pauli as the RM for 5.5.

Huge +1.

When we discussed that, you wanted to give up your role with 5.4 (one
is enough at this point) and be  co RM for 5.5. Did you change your
mind?

Cheers,
Pierre