Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102425
Return-Path: <cmbecker69@gmx.de>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 2004 invoked from network); 25 Jun 2018 14:57:05 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 25 Jun 2018 14:57:05 -0000
Authentication-Results: pb1.pair.com smtp.mail=cmbecker69@gmx.de; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=cmbecker69@gmx.de; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.21 as permitted sender)
X-PHP-List-Original-Sender: cmbecker69@gmx.de
X-Host-Fingerprint: 212.227.17.21 mout.gmx.net  
Received: from [212.227.17.21] ([212.227.17.21:42555] helo=mout.gmx.net)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id C6/E7-50433-0C2013B5 for <internals@lists.php.net>; Mon, 25 Jun 2018 10:57:04 -0400
Received: from [192.168.2.114] ([87.167.207.88]) by mail.gmx.com (mrgmx101
 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Lbi2Z-1g0W8W0dKt-00lFrh; Mon, 25
 Jun 2018 16:56:59 +0200
To: Zeev Suraski <zeev@zend.com>, internals <internals@lists.php.net>
References: <DM5PR0201MB354280334D34629059189156AC4A0@DM5PR0201MB3542.namprd02.prod.outlook.com>
Message-ID: <3dd3fe15-5797-f450-62b2-37cc154b03f7@gmx.de>
Date: Mon, 25 Jun 2018 16:57:00 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <DM5PR0201MB354280334D34629059189156AC4A0@DM5PR0201MB3542.namprd02.prod.outlook.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K1:iRoItPaDDP4VEj72kvupzRvLvrEiz2yGdRVgYxPBRPe+X8S3H6g
 7fvayopZVNexax7VsZyRIcImT0JNiTtiEIdAdttQOGe0plfXPBreTYDKMm0k3y2Z7yxWB9y
 i5BQG3VW3oD2Gj4om16AruHFGGBcuSgzrNDDo+yris0/gUXXfgSnUkiQuoeKHuiMJsTLrUT
 gzJoc3X01EwW8+wJnGnqQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:G8R7CQa3EGM=:Og7XR59AYtltm/3oqbkk9b
 mz3ioTRtIse0yAVMd8m3HfFeD2hqusWjab53u7OOYR657w84fV3c7ARHnYmFcAmdPnSsNnwyn
 j5a1zz6ZliXc+wLmZ8jqq6Gn+d3/X/O22lozKQep9U7+99E+prG+vONwV3HT38hT+rt4mA+Tc
 w0iMTipZGXtc8pijU68FpvXX1qjACfUsUqKShHi0WJjEZHuXBrvTQr4YyRjj8KzBcJzrC5wYD
 dPzVumWDgwpbdeZBvriRzkcvfttuzIeMAUYsdcr0k6ogKiTKfnrWcU8ryzgbJjoxVNrnuffYD
 pdCwUeO8nJijROX+tcjyt3ORwZ3d6H8LVKaYznJr9bRYJ9Dk/TGm3zUTSpTWWmbb6xGyoh89G
 U6LJu1xw3EmjMxJeT2EcWUwfeovRqWsprYPOPK91nJBO06JBjcrqRh8h1mJGB8DFJJVMS5UiZ
 lrnBDDORQzAhX54BUHPY1lUXG2GARicbE0TiLhYAQU5M6Y0W30U0qbCYq+khYg5FIdauPEuej
 pOBkE0+vUy9Clc4e4uY7nC7vf7B1Y3NsS3LdB6wKoLiyCzE/GHbgb9/B8yekuiXTH5shNsuxz
 +obF4z391JViFmauzFr/rHQHe4gGCMf3gRZc3ad9rcia1cnsp4wAcluoEgXGE+gjD94Y7+d1m
 RfoNNaiqD66oWKw/o6h5IE5hov1vqnYFnYGC6W7DqqxrTUqohxU9Jf4E/4bKjUwz7qg5MfWyx
 aLbykQVm4NMK2UNGZhfJoDUre7rE8q4Vky2EwWLDWGxIKTe2v0rrP+C3CwLyXFm5GnTwmAtwY
 etfomTP
Subject: Re: PHP 2^3
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 25.06.2018 at 14:30, Zeev Suraski wrote:

> What this list is - a collection of directions around which we've performed varying amounts of research (some of them quite a lot, like JIT), that I think is strong grounds for us to start discussing a PHP 8 timeline, and making PHP 7.3 the last feature release in the PHP 7.x family.  If we had to come up with an educated guess as to when PHP 8 could be ready to be released based on the abovementioned featureset, we're probably talking about 2-2.5yrs away (i.e. mid/late 2020).  We can also consider having a very slim PHP 7.4 release sometime in 2019 that wouldn't add any functionality, but that would give us an opportunity to deprecate anything that we missed in 7.3 that truly requires deprecation - while still allowing folks to prepare for 8.0 ahead of time.

Why not stick with our yearly release cycle, and ship 7.4.0 in Dec 2019
and 8.0.0 in Dec 2020?

-- 
Christoph M. Becker