Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75305 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 14917 invoked from network); 7 Jul 2014 13:05:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Jul 2014 13:05:56 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.51 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.192.51 mail-qg0-f51.google.com Received: from [209.85.192.51] ([209.85.192.51:35724] helo=mail-qg0-f51.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 20/A3-21356-33B9AB35 for ; Mon, 07 Jul 2014 09:05:55 -0400 Received: by mail-qg0-f51.google.com with SMTP id z60so3620589qgd.24 for ; Mon, 07 Jul 2014 06:05:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ovG34JOvFTzIXp9wZ6eiq1AB0kvbWsXuxHcDaBklkHY=; b=S7kmveBut9VD3BKxsOHRwhp/ZuQB87eAAyREJdQ4Z7elin9SH1+AI/8a251swqQg+v HuImEHZZASsYbWPUiYOdPxR0xVsI6DIWoeXBeji2tKJ3bbSf8Jmxy2p6NbeHnrZOxecm gdBgLoJ2IksYVauYEPtJnq87MFBf55sFyMS/FL6tsJxuiVXFGLCOQmMIDFBFdVfJanYU IhFsLMgfXs1FUr3W826NOLWNoW2RsyNNuDl01ifZcI/Ri+Otwa1PfBVYn7Jo9V/n04hf HZsly3GUZlqJFLx1jG7iotpwoziPssDqm9l/VJpoyIYLILtHp7QrRATMQkM6uBewETs/ xjLw== MIME-Version: 1.0 X-Received: by 10.140.49.76 with SMTP id p70mr44330781qga.86.1404738352899; Mon, 07 Jul 2014 06:05:52 -0700 (PDT) Received: by 10.140.28.183 with HTTP; Mon, 7 Jul 2014 06:05:52 -0700 (PDT) Received: by 10.140.28.183 with HTTP; Mon, 7 Jul 2014 06:05:52 -0700 (PDT) In-Reply-To: <1581132639526056444@unknownmsgid> References: <61EEC54E-7B8D-433E-A391-75F8D6A41E79@ajf.me> <650742796f119ed972a688a58e02242b@mail.gmail.com> <53BA8E93.8060708@lsces.co.uk> <1581132639526056444@unknownmsgid> Date: Mon, 7 Jul 2014 15:05:52 +0200 Message-ID: To: Zeev Suraski Cc: Lester Caine , PHP internals , Andrea Faulds Content-Type: multipart/alternative; boundary=001a11370a3486f52304fd9a22d1 Subject: Re: [PHP-DEV] [RFC] Name of Next Release of PHP From: pierre.php@gmail.com (Pierre Joye) --001a11370a3486f52304fd9a22d1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable And here we go. So basically you are saying that once phpng is stabilized, no matter the api/SRC cleanness, we are good for next. This is very bad and I will vote -1 on anything close to this idea. Besides that, the same kind of estimation was done for opcache, which was a much smaller beast. They went bad by 300%, just saying. On Jul 7, 2014 2:57 PM, "Zeev Suraski" wrote: > > On 7 =D7=91=D7=99=D7=95=D7=9C 2014, at 08:50, Andrea Faulds wrote: > > > > > > The problem is that people who want to add stuff for PHP 6 feel they > have to add it to phpng, because if phpng is to be PHP 6, then it would > need to be based off that branch. > > > > I don't think it's a problem, because I don't think we're two years > away from releasing a phpng-based version and I don't think it's a > moving target at this point. So I agree we need to remove these > uncertainties. > > I'm going to start an RFC-based discussion for moving phpng to master > so that the uncertainties around it are removed. > > Zeev > --001a11370a3486f52304fd9a22d1--