Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71203
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.54 as permitted sender)
MIME-Version: 1.0
Sender: tyra3l@gmail.com
In-Reply-To: <CAH-PCH5bTUqPxRZCuDHKumhZu9TRONFnBMkkHLBN-b+4dk-VEg@mail.gmail.com>
References: <CAH-PCH7n-6YaSCE+PG01TD9z4ArxzQkUK5wJbXjK=cqmj-xkjw@mail.gmail.com>
	<CADajX4Cx3RxoVdLoao69MTDe1PXWgsLaRu_sttY8bra7sJMYyQ@mail.gmail.com>
	<CAH-PCH7ciKdL713vz8+wfbY40eKbxyXTeRZZs=6r2g-ScJ3abA@mail.gmail.com>
	<CAMUwpuR3=30XSisLQv1wnDtDLFdXfehLtsH_g+cKSWDwi75vJg@mail.gmail.com>
	<CAH-PCH5bTUqPxRZCuDHKumhZu9TRONFnBMkkHLBN-b+4dk-VEg@mail.gmail.com>
Date: Fri, 17 Jan 2014 10:05:40 +0100
Message-ID: <CAH-PCH5F0x53CeDrVVP0Mp7CdUUQQMWtFCET8mfsrVK1w9Cr-w@mail.gmail.com>
To: Julien Pauli <jpauli@php.net>
Cc: Adam Harvey <aharvey@php.net>, PHP Internals <internals@lists.php.net>, 
	David Soria Parra <dsp@php.net>
Content-Type: multipart/alternative; boundary=001a11c0371aa0f32d04f026d88d
Subject: Re: [PHP-DEV] Proposed timetable for PHP 5.6.0
From: tyrael@php.net (Ferenc Kovacs)

--001a11c0371aa0f32d04f026d88d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 15, 2014 at 4:33 PM, Ferenc Kovacs <tyrael@php.net> wrote:

>
>
>
> On Fri, Dec 13, 2013 at 1:41 PM, Julien Pauli <jpauli@php.net> wrote:
>
>> On Fri, Dec 13, 2013 at 7:56 AM, Ferenc Kovacs <tyrael@php.net> wrote:
>> >
>> > 2013.12.12. 19:48, "Adam Harvey" <aharvey@php.net> ezt =C3=ADrta:
>> >
>> >
>> >>
>> >> On 12 December 2013 04:23, Ferenc Kovacs <tyrael@php.net> wrote:
>> >> > As you probably all remember the first beta usually means feature
>> >> > freeze,
>> >> > so no new additions are allowed, only fixes, so the code can
>> stabilize
>> >> > in
>> >> > the beta and RC phase.
>> >> > Learning from the past we would also like to introduce a new rule
>> about
>> >> > not
>> >> > accepting new RFCs targeting 5.6.0 after the first alpha is shipped=
,
>> >> > because given the discussion and voting period it can force us into=
 a
>> >> > spot
>> >> > where we have to chose between
>> >>
>> >> I like this: +1.
>> >>
>> >> If it works well, then we probably want to announce the calendar a
>> >> little earlier for the 2015 release, since there's now a pretty narro=
w
>> >> window to propose an RFC and have it voted on before January 16. By m=
y
>> >> estimation, an RFC will have to enter "in discussion" by December 26
>> >> (hope nobody has plans over the holidays) to be accepted for PHP 5.6,
>> >> assuming minimal two week discussion and one week voting periods.
>> >
>> > Nope, you can introduce RFCs until the first alpha, RFCs under
>> discussion or
>> > under voting are allowed to be added (until the first beta).
>> >
>> > Ofc. this still leaves with only a month, which also includes
>> chirstmas/new
>> > year so not that much time, but we are already a bit behind schedule.
>>
>> Yup, with Christmas and all, that will slow things down.
>> We still can accept little delays, we all are humans, but not a one mont=
h
>> delay.
>> We must release final on June
>>
>> Julien
>>
>
> Hi,
>
> I plan to tag the the first alpha today, and release it tomorrow, so the
> time for new RFCs are almost up.
>

Hi,

I had to recreate my dev environment as my home desktop got some hardware
issues, and I didn't wanted to tag the release without a bit more testing.
Hopefully I can tag the release today, and I will talk with Julien and the
windows build guys about the next possible release date.

Sorry for the delay!

--001a11c0371aa0f32d04f026d88d--