On Mon, Jul 21, 2014 at 5:28 PM, Xinchen Hui <larue...@gmail.com> wrote:
> Hey: > > > 在 2014年7月21日，19:02，Ferenc Kovacs <tyr...@gmail.com> 写道： > > > >> On Mon, Jul 21, 2014 at 12:31 PM, Zeev Suraski <z...@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 think > >> 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’t see a reason of why we can’t have this major version 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 � we’re likely to needlessly > >> delay .NEXT… > >> > >> > >> > >> 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. -- Ferenc Kovács @Tyr43l - http://tyrael.hu
