Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75806
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <-6299216022086038902@unknownmsgid>
References: <b39ebab3d19d76cda9bafa25919c0e67@mail.gmail.com>
	<CAGa2bXahqscNFe5Dy7Lc6NcjZDfw+tkNBtM8Z8p-+n7anq8gew@mail.gmail.com>
	<df087915cfde8c749fd9551953a3ca40@mail.gmail.com>
	<CAH-PCH7jd6D=sP6MaAD4tK-F0SRXpWj3_bzie9y5ZqeL-Gi3cA@mail.gmail.com>
	<aa6e605aa20062ea943b550d342ae222@mail.gmail.com>
	<CAH-PCH7jHQK4w3cqqf3S+HrxbjY_jHNCUJY5OpB6oH7VNQJn=A@mail.gmail.com>
	<-6299216022086038902@unknownmsgid>
Date: Mon, 21 Jul 2014 18:10:03 +0200
Message-ID: <CAH-PCH4pxuWDk7sFudHix_OeVVfusUYZ6i89kKCOaGSSJNFBeA@mail.gmail.com>
To: Xinchen Hui <laruence@gmail.com>
Cc: Zeev Suraski <zeev@zend.com>, Yasuo Ohgaki <yohgaki@ohgaki.net>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c21edafcc3a204feb6566f
Subject: Re: [PHP-DEV] RFC: Move phpng to master
From: tyra3l@gmail.com (Ferenc Kovacs)

--001a11c21edafcc3a204feb6566f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Jul 21, 2014 at 5:28 PM, Xinchen Hui <laruence@gmail.com> wrote:

> Hey:
>
> > =E5=9C=A8 2014=E5=B9=B47=E6=9C=8821=E6=97=A5=EF=BC=8C19:02=EF=BC=8CFere=
nc Kovacs <tyra3l@gmail.com> =E5=86=99=E9=81=93=EF=BC=9A
> >
> >> On Mon, Jul 21, 2014 at 12:31 PM, Zeev Suraski <zeev@zend.com> wrote:
> >>
> >>
> >>
> >> He just asks if we will have a 5.7 release while working on the next
> major
> >> in master.
> >>
> >> I don't think that we can release the php-next under a years, so I thi=
nk
> >> that an 5.7 could be warranted (to keep up with our roadmap), but
> depends
> >> on wether or not we have enough new (BC-safe) features.
> >>
> >> I don=E2=80=99t see a reason of why we can=E2=80=99t have this major v=
ersion ready by or
> >> even sooner than the current yearly rhythm we have.  In fact, if we do
> aim
> >> to work in parallel on both 5.7 and .NEXT =EF=BF=BD we=E2=80=99re like=
ly to needlessly
> >> delay .NEXT=E2=80=A6
> >>
> >>
> >>
> >> Zeev
> >
> > because there is so much stuff which we want to do in the next major
> > version, but we can't even start because there is no stable base to
> target
> > the other php-next features.
> What they are?  Please come with RFC and Patches.
>

https://wiki.php.net/rfc/uniform_variable_syntax
https://wiki.php.net/rfc/size_t_and_int64_next


> Or you suggest we stop the current work to waiting them come their self?
>

I'm saying that we should resolve the current situation where people can't
work on stuff which would target php-next, because it is still a moving
target.
I'm saying that it is nice that you(the phpng main devs) are confident that
you can stabilize your changes so making a php-next release in less than a
year, but other people have other ideas which can only happen in a major
version, and you shouldn't rush an early release which would mean that the
next window of opportunity for major refactor is in the next decade.
I'm saying that it is pretty unfortunate that we have to decide to between
reviewing/accepting a huuuuuuuge chunk of changes or rejecting a
significant performance boost and some api cleanup.
I'm saying that we should stop pushing our own agendas, and figure out the
best possible solution for the current situation, so that we can go forward
with the development with the normal workflow, where everybody is on the
same page, controversial changes are done through RFCs and we don't block
each other from the work.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--001a11c21edafcc3a204feb6566f--