Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102433
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.177 as permitted sender)
MIME-Version: 1.0
References: <DM5PR0201MB354280334D34629059189156AC4A0@DM5PR0201MB3542.namprd02.prod.outlook.com>
 <CAESVnVpcd7xBB+A+6Kz0b5JqnPaZfQitWLtXi-4_cZA8kf2knw@mail.gmail.com>
 <CAJHtznzVSPLLvGJW471GoKbBE7uB5oLYJ+8Lq-=vYSP-LHeYww@mail.gmail.com> <CAESVnVpC8KyHP4rOm=Ne_MfOC2Nr_jB_RKUKDDAkFdbTggeV3Q@mail.gmail.com>
In-Reply-To: <CAESVnVpC8KyHP4rOm=Ne_MfOC2Nr_jB_RKUKDDAkFdbTggeV3Q@mail.gmail.com>
Date: Mon, 25 Jun 2018 20:31:53 +0300
Message-ID: <CAJHtznxZECZf8qbe7zSgEb0gngVDA0oWWs0otncWts=K=W7mrA@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: Zeev Suraski <zeev@zend.com>, internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000008ba660056f7ac226"
Subject: Re: [PHP-DEV] PHP 2^3
From: vsuraski@gmail.com (Zeev Suraski)

--0000000000008ba660056f7ac226
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 25, 2018 at 7:16 PM Sara Golemon <pollita@php.net> wrote:

> Yeah, like I said, I must have completely missed that entire
> paragraph.  Mid-2020, following a late-2019 release of a "light" 7.4
> with deprecations is reasonable, though I don't think it'd be such a
> bad idea if we kept it on schedule to GA 8.0 with all the goodies in
> Nov 2020.  As alluded, I kind of like that FF happens in the summer
> when things *should* be relatively slow otherwise.
>

Well, my guesstimate for the timeline was actually 2-2.5yrs from now, so
that's ranging from mid 2020 to late 2020.  You have a point that releasing
in summer isn't the smartest thing to do, so planning to hit later in that
year probably makes sense.  I think we should probably keep ourselves some
flexibility on the final date as we see how the different projects progress
- perhaps September through December 2020.

And based on the timetable that I realize I should have seen but
> missed, you've got my vote.
>

Awesome!


> > I still think that Dmitry's idea that we have a deprecation-only 7.4
> > sometime in 2019 makes sense.  If we really wanted to we could make it =
a
> > deprecation+some extras version, but I'm concerned about fragmenting ou=
r
> > scarce resources.  I don't think the sky will fall in case we take 18-2=
4
> > months between our last 7.x feature release and 8.0.  We've had that
> between
> > 5.6 and 7.0 and I think it worked pretty well.
> >
> I'm not against some features for 7.4.  I'd even say Niki's typed
> properties (which isn't a minor change) can slot in there happily
> enough.  But we can dig in deeper over time on that.  Maybe he gets it
> into 7.3? =C2=AF\_(=E3=83=84)_/=C2=AF
>
> Personally I don't think that's 7.3 material, even when factoring out my
dislike for scalar properties in the way they're currently implemented, and
I think there's value in putting something as substantial as that in the
major version as another 'attraction point' for people to migrate.  I'm
sure we'll discuss it thoroughly...

By the way, perhaps weak STH are another thing we can revisit for 8 - looks
like there were quite a few surprised folks out there regarding their
current behavior, and that implementing them closer to the old Coercive STH
RFC might be useful (without affecting the strict STH).  Not sure I have
the mental strength for that though :)

Zeev

--0000000000008ba660056f7ac226--