Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75808 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84512 invoked from network); 22 Jul 2014 01:42:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Jul 2014 01:42:31 -0000 Authentication-Results: pb1.pair.com header.from=laruence@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=laruence@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.52 as permitted sender) X-PHP-List-Original-Sender: laruence@gmail.com X-Host-Fingerprint: 209.85.215.52 mail-la0-f52.google.com Received: from [209.85.215.52] ([209.85.215.52:51740] helo=mail-la0-f52.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C0/30-14611-481CDC35 for ; Mon, 21 Jul 2014 21:42:29 -0400 Received: by mail-la0-f52.google.com with SMTP id e16so5276912lan.25 for ; Mon, 21 Jul 2014 18:42:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=oD4+Y6Ueg4ffu0PtnZpkDNH7fFqpFcH3s9fefC0PWzo=; b=Jy+nhHv1ttCe2eOGBeLMiNbrLTEorJ5414mTDSpBZ5/I+EE3BmfCVpAotBCTDWclKc nojej75OvgJ5BIogGExCGX/Jx8poFGGDWNCpdAF27VCRkT4HwBgDI+O/M9WspdfiAfZ6 +7Pwp7cwN2ch2MEtD48nPFceAOh7Dgcfttfqg6sCtzYs5YN0cbsoyaCcIFCC3h3Jjr4j Uciz3f3pURdL3M4M9vzX/7ecNUcgw9zz9Sdw6wULborP8saalAIy9mt3ff0p2EEmgoxl SYNj+SU02I6gfbcTjkwWa4Kd9H943FPujUDhGJ8j9e8LZO7Tn0rB0v66/3vnSsyhD2c6 M+Cw== X-Received: by 10.152.116.105 with SMTP id jv9mr2960138lab.47.1405993345283; Mon, 21 Jul 2014 18:42:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.187.207 with HTTP; Mon, 21 Jul 2014 18:42:05 -0700 (PDT) In-Reply-To: References: <-6299216022086038902@unknownmsgid> Date: Tue, 22 Jul 2014 09:42:05 +0800 Message-ID: To: Ferenc Kovacs Cc: Zeev Suraski , Yasuo Ohgaki , PHP internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] RFC: Move phpng to master From: laruence@gmail.com (Xinchen Hui) Hey: I really don't like arguing in english, so this will be my last reply in this thread. On Tue, Jul 22, 2014 at 12:10 AM, Ferenc Kovacs wrote: > > > > On Mon, Jul 21, 2014 at 5:28 PM, Xinchen Hui wrote: >> >> Hey: >> >> > =E5=9C=A8 2014=E5=B9=B47=E6=9C=8821=E6=97=A5=EF=BC=8C19:02=EF=BC=8CFer= enc Kovacs =E5=86=99=E9=81=93=EF=BC=9A >> > >> >> On Mon, Jul 21, 2014 at 12:31 PM, Zeev Suraski 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=E2=80=99t see a reason of why we can=E2=80=99t have this major = version ready by >> >> or >> >> even sooner than the current yearly rhythm we have. In fact, if we d= o >> >> aim >> >> to work in parallel on both 5.7 and .NEXT =EF=BF=BD we=E2=80=99re lik= ely 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 aren't they discussed and voted? what do you mean by we can't even start in previous comment? > >> >> 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. why Nikita could work on it? why me can work on it? > I'm saying that it is nice that you(the phpng main devs) are confident th= at > 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 th= e > next window of opportunity for major refactor is in the next decade. I am not sure about you attitude here, from these words, seems you agree to merge phpng to master asap, then people can start work on it? > I'm saying that it is pretty unfortunate that we have to decide to betwee= n > reviewing/accepting a huuuuuuuge chunk of changes or rejecting a signific= ant > performance boost and some api cleanup. we shouldn't, at least most people here shouldn't, only the guys who need to maintain them should. > I'm saying that we should stop pushing our own agendas, and figure out th= e > best possible solution for the current situation, so that we can go forwa= rd > 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. you know what? I really don't like "we should; we must", they means nothin= g.. I have spent lots of my time to work on PHP/PHPNG, more than 80 hours per month. I treat it like a regular work, dmitry spends more than me(8 hours per day)= . you ask me to stop to wait somebody who even can not work hours a month her= e? with all my respects: I really upset by people who always told you, hey man, don't be rush... because I am rushing, I have be rushing for months to make the work done.. last of all : "all above is my personal comments, has nothing to do with Zend"... thanks > > -- > Ferenc Kov=C3=A1cs > @Tyr43l - http://tyrael.hu --=20 =E6=83=A0=E6=96=B0=E5=AE=B8 laruence Senior PHP Engineer http://www.laruence.com