Re: RFC: PHP 7.0 timeline
| From: | Julien Pauli | Date: | Wed, 15 Oct 2014 08:13:06 +0000 |
| Subject: | Re: RFC: PHP 7.0 timeline | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-78090@lists.php.net to get a copy of this message | ||
On Wed, Oct 15, 2014 at 2:39 AM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
> On 10/14/2014 05:20 PM, Tjerk Meesters wrote:
>>
>> On 15 Oct 2014, at 01:24, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
>>
>>> On 10/14/2014 10:14 AM, Stas Malyshev wrote:
>>>> Hi!
>>>>
>>>>> IMO, AST, INT64, NG, Uniforme variables style is enough for a new
>>>>> marjor version.. why we still need to wait?
>>>>
>>>> We don't need to just "wait", as sit and do nothing. We need to
>>>> allocate
>>>> time for other features.
>>>
>>> There are also quite a few really low-level changes in master right now.
>>> It is going to take quite a bit of time to stabilize. For example,
>>> something as basic as array iteration is inadvertently different:
>>>
>>> https://bugs.php.net/68215
>>
>> This is a known issue for which the test cases were marked as XFAIL because of the amount
>> of work involved to get it fixed:
>>
>>
>> https://github.com/php/php-src/commit/5831cca9576f4e0d4daed75a9915d436dfc5f4e5
>
> Yes, I am aware of that. I was using it to illustrate the point that
> even with the changes currently in master, never mind any new things we
> might add, we have a lot of work left to do before we are anywhere near
> ready for a release.
I agree, we must absolutely provide something stable, solid,
performant and feature rich.
This will take time to stabilize and spot edge cases, some of them
could even lead to a reverse somewhere in the code.
Julien.Pauli