Re: Proposed timetable for PHP 5.6.0
| From: | Julien Pauli | Date: | Wed, 15 Jan 2014 15:48:19 +0000 |
| Subject: | Re: Proposed timetable for PHP 5.6.0 | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-71142@lists.php.net to get a copy of this message | ||
On Wed, Jan 15, 2014 at 4:43 PM, Ferenc Kovacs <tyra3l@gmail.com> wrote:
> On Wed, Jan 15, 2014 at 4:36 PM, Philip Sturgeon <pjsturgeon@gmail.com>wrote:
>
>> I'm writing one up literally as we speak. Any chance of a hard
>> deadline on time to get it done by, or maybe pushing it back a day?
>>
>>
> I don't wanna be too strict about this, if you can put it up for discussion
> this week (and make sure that it is implemented and voted before the first
> beta) then it will make it.
> We just don't want to handle a situation when everybody comes up with new
> RFCs in the last minute before the feature freeze.
Yep, that's to prepare for the future.
We *won't* merge any RFC after the first beta. Recall that everybody.
If you now have a new RFC, ok why not accept it in the 5.6 workflow
(even if we said no new RFC after first alpha) , let's not be too
strict, but be warned it *has to* be merged before first beta , that
is something like mid-march.
For sure, no new idea can be merged after first beta, so RFC will have
to be stabilized and voted and accepted for the mid-march dead-line.
Several betas will then happen to fix last bugs in the implementations.
Thx,
Julien.Pauli