Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75804 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52856 invoked from network); 21 Jul 2014 15:28:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Jul 2014 15:28:22 -0000 Authentication-Results: pb1.pair.com smtp.mail=laruence@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=laruence@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.175 as permitted sender) X-PHP-List-Original-Sender: laruence@gmail.com X-Host-Fingerprint: 209.85.217.175 mail-lb0-f175.google.com Received: from [209.85.217.175] ([209.85.217.175:63991] helo=mail-lb0-f175.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C7/C9-01457-4913DC35 for ; Mon, 21 Jul 2014 11:28:20 -0400 Received: by mail-lb0-f175.google.com with SMTP id 10so1699205lbg.6 for ; Mon, 21 Jul 2014 08:28:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:from:mime-version:in-reply-to:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=oJkmSlhMbmHqklQgoMB1S0j6cmWpchPdO7O0H1xZGhY=; b=Mmuxhgst8sUrBXL/kUBB2TEtIodGPthaZAetotxgR4mmaHmTm7RGkl3kMlPJ9Lkjz0 6+SSvrQisPlcCKBWXTml9zkm4JC00cO9aUlnbZoaLTgxMqbi38Imwev+xBweRwp1d493 KYumbBeIP6Mubc6LEczmsNvZtosp94Sa43zrVCOZocChwoFlTiF9fZeUb47NGKGWgDOn SfD4/FYItuLyGYUX9B8yInrgxkakH8V+g3Ns/hskcpm3Y2ADdSy7HkvHypKOawOd/RkX +9kPNqASS9aFhXHtABWWWoujdTR6E8fpk8MxBRYyIQT9ZlumFtqTt/PIqkvwmqpwj4TB eL7A== X-Received: by 10.152.6.170 with SMTP id c10mr27258192laa.9.1405956496437; Mon, 21 Jul 2014 08:28:16 -0700 (PDT) References: Mime-Version: 1.0 (1.0) In-Reply-To: Date: Mon, 21 Jul 2014 23:28:14 +0800 Message-ID: <-6299216022086038902@unknownmsgid> 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: > =E5=9C=A8 2014=E5=B9=B47=E6=9C=8821=E6=97=A5=EF=BC=8C19:02=EF=BC=8CFerenc= 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 maj= or >> 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 depend= s >> 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 ver= sion ready by or >> even sooner than the current yearly rhythm we have. In fact, if we do a= im >> to work in parallel on both 5.7 and .NEXT =EF=BF=BD we=E2=80=99re likely= 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 targe= t > the other php-next features. What they are? Please come with RFC and Patches. Or you suggest we stop the current work to waiting them come their self? Thanks > based on the history of php versions, any feature which misses php-next > will have to wait for the next decade, so I don't think that we should ru= sh > it (to meet our yearly release cycle defined in > https://wiki.php.net/rfc/releaseprocess). > > -- > Ferenc Kov=C3=A1cs > @Tyr43l - http://tyrael.hu