Hi David,

On Tue, Jul 22, 2014 at 2:08 PM, David Soria Parra <d...@php.net> wrote:

> On 2014-07-21, Michael Wallner <m...@php.net> wrote:
> > --001a11345984e013cd04feb0d9a1
> > Content-Type: text/plain; charset=UTF-8
> > Content-Transfer-Encoding: quoted-printable
> >
> > On 21 Jul 2014 10:21, "Julien Pauli" <jpa...@php.net> wrote:
> > PHP-Next.
> >
> > I don't think that a cleanup is nearly as important as php-ng is as we
> > stand currently.
> >
> > The will be no mercy from the competition.
> >
> > We can start reworking the API when it hit master.
> >
> > --001a11345984e013cd04feb0d9a1--
>
> I want to remind that the last attempt of PHP 6 died because it was mostly
> unmaintained as "master" for a long time and we continued to postpone
> it. We should try to not again make a "big move" but take "babysteps"
> and focus on phpng and 64bit as the major features and not maintain a
> branch while we are doing 5.7. This will undoubtful lead to a similar
> "abundance" of the master branch as we just don't have the ressources
> to maintain more branches (a point already made when we discussed the
> release plan).
>
> I think we should consider steps to make phpng the major development
> branch within the year and if stabelizing it within the year possible,
> make it the next release.
>

Even if we have PHP-5.7 branch, we have merge up policy. Therefore,
any new feature will end up with master, I suppose. If a new feature is
only available to PHP-5.7 branch, it's a merge bug, isn't it?

Regards,

--
Yasuo Ohgaki
yohg...@ohgaki.net

Reply via email to