Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75786 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 18439 invoked from network); 21 Jul 2014 12:32:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Jul 2014 12:32:08 -0000 Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 74.125.82.49 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 74.125.82.49 mail-wg0-f49.google.com Received: from [74.125.82.49] ([74.125.82.49:55284] helo=mail-wg0-f49.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7A/13-01457-3480DC35 for ; Mon, 21 Jul 2014 08:32:05 -0400 Received: by mail-wg0-f49.google.com with SMTP id k14so6310582wgh.20 for ; Mon, 21 Jul 2014 05:31:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:in-reply-to:mime-version :content-transfer-encoding:content-type:message-id:cc:from:subject :date:to; bh=0kIVSQwtFnN5x0mzrKiLZzM562i8r2CAUlAHjUC99oY=; b=NAKpyT+YmIzUhoZJU8LTgXkVJHQXnlx5LQUeiGSP5hVESEaGggDJB4rjUc6udvGNr8 WfWYhnSr2UqT9hIYLLygVasYGzj76a1FezWoHRWUuBe9Myc9eZOxWxxeIsoQi3da+Wiq NY8Gfpz8MHwrX2BMea1Em/5cejlrrObmSRyFiCh8Z3OAJq/JvJpmi1j4eu1XfPjat/s7 VvC/qlh01kS6vaMCAfD5aIVTzN9N+CXba/MGCe85c7lP1Oze6XnE1qYnePIQnF1lZdDY tnmCXmQdK+9SuyI29Jq46EpgE6EQJDf6+pk/VKDWwgQy/5kkvOR7N7b3n2VFILsbEx/K znSA== X-Gm-Message-State: ALoCoQkRPcR1TqFw6QoaXDEtfUL2I/Ugv4evma7pmp0PLzF3z72lgQ0aAUKeqkUoBy9ByO5CGTP7eEO23bRr9gisvzeHxhEOgSE4SyAIPB97cHZO3e5iE2rZX/6ydf5ZNO/be5HoVdRu X-Received: by 10.180.84.2 with SMTP id u2mr3853680wiy.27.1405945918807; Mon, 21 Jul 2014 05:31:58 -0700 (PDT) Received: from [10.1.2.78] (il-gw1.zend.com. [212.199.177.67]) by mx.google.com with ESMTPSA id bg2sm41506702wib.21.2014.07.21.05.31.57 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Jul 2014 05:31:57 -0700 (PDT) References: In-Reply-To: Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary=Apple-Mail-88391110-4EA6-4ABD-8B47-278D64335D5A Message-ID: Cc: Nikita Popov , PHP internals X-Mailer: iPad Mail (9B206) Date: Mon, 21 Jul 2014 15:31:57 +0300 To: Ferenc Kovacs Subject: Re: [PHP-DEV] RFC: Move phpng to master From: zeev@zend.com (Zeev Suraski) --Apple-Mail-88391110-4EA6-4ABD-8B47-278D64335D5A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On 21 =D7=91=D7=99=D7=95=D7=9C 2014, at 14:20, Ferenc Kovacs wrote: > On Mon, Jul 21, 2014 at 1:10 PM, Nikita Popov wrote= : > On Mon, Jul 21, 2014 at 9:31 AM, Zeev Suraski wrote: >=20 > > All, > > > > As we=E2=80=99re getting closer to release 5.6.0, and given the very hig= h level of > > interest in phpng, I think it=E2=80=99s time for us to provide some clar= ity > > regarding what happens post 5.6.0. > > > > Dmitry and I wrote an RFC proposing that we merge phpng into master and > > turn it into the basis of the next major version of PHP (name TBD). > > > > The RFC is available at https://wiki.php.net/rfc/phpng > > >=20 > There are actually two questions here: > 1. Do we want to base the next major version on phpng? > 2. Do we want to merge phpng into master? >=20 > The latter is tied to the question whether or not we want to have a PHP 5.= 7 > release in the meantime. I'm not really sure whether or not that would be > good, I would recommend opening a separate thread about that question. >=20 > either way, master should/will contain the changes from phpng, otherwise w= e would go against to our current merge everything upwards git workflow. Agreed. > but that doesn't really a problem for 5.7, we should just branch it from 5= .6 (we wanted to do this for 5.6 and 5.5, but most of the changes in master a= t that time was ok for a minor, so we branches from master instead of cherry= picking everything.), as anything we want to backport from master to 5.7 wou= ld require manual work to make it compatible with 5.7. Agreed too - I just think we should first focus on getting .NEXT released as= soon as possible - and only branch away a 5.7 if we see it's taking too lon= g. It's not a decision we need to take today, but if we were to do it, bran= ching it from 5.6 sounds like the right way to do it. Zeev= --Apple-Mail-88391110-4EA6-4ABD-8B47-278D64335D5A--