Re: Moving forward: PHP 5.5
| From: | David Soria Parra | Date: | Sat, 08 Sep 2012 14:20:13 +0000 |
| Subject: | Re: Moving forward: PHP 5.5 | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-62906@lists.php.net to get a copy of this message | ||
On 2012-09-08, Pierre Joye <pierre.php@gmail.com> wrote:
> 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.
I agree. I missed the point that 5.5 should not include bc breaks either.
>> 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.
>>
>> 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?
As some people are confused by what I mean with what I would do. I
can help with 5.5 and be the Co-RM again. The reason is simple, while
the main RM is bound to the series for 2-3 years, Lukas back then and
now I realize that after the first bumpy months it's a fairly straight
forward job (particularly thanks to the release process) and I am sure
Stas can manage 5.4 on it's own (and in case he is away for two weeks
i can still run the process). At that point I am bascially just doing
the announcements for 5.4.