On Fri, Jan 24, 2014 at 11:22 AM, Adam Harvey <[email protected]> wrote:
> On Jan 24, 2014 5:44 PM, "Nikita Popov" <[email protected]> wrote:
>> My schedule recommendation would be to give PHP6 at least two years after
> 5.6. After all, it's a larger change, so we'll presumably need more time.
>
> It is, but I'm also wary of having too big a gap between starting work and
> releasing. Plugging away for years without a release is really
> demoralising, as the PHP 6 experience showed. If anything, I feel like 18
> months between 5.6 and 5++ is longer than ideal, but I think staggering the
> release timing is worthwhile.
>
>> Is there any problem with using the current master branch as PHP6 right
> away? 5.7 (should it exist) can be branched off 5.6 after all.
>
> We already have things that are likely to end up in 5.7, I think — I'd
> rather have a 5.x-master rather than forcing developers to maintain long
> lived feature branches for things that are 5.x material but not going into
> 5.6.
Hah finally a serious talk about next major, with no (not yet) trolls in it..
We have to release a new major , or at least to start thinking about
it seriously.
5.3 and 5.4 could have been majors by themselves, as they really fully
changed the way you develop PHP apps.
Like Nikita said, we have enough new (BC breaking) features and ideas
to start PHP5++
I'd like to add that I'd like to use this major to introduce some
clean-up as well, should they be internal or external.
We're gonna break BC, let's do it in a way so that we start back with
a new clean code base, like when PHP5.0 got released, with a new Zend
Engine 2 inside.
Let's use this major to refactor internals code and finally tidy up
things as well in external API.
Julien.P