This was a continuation of a previous thread, but I felt my notes below
warranted splitting off into a new thread.
Hi
On Tue, Jul 5, 2022 at 7:09 PM Pierrick Charron pierrick@php.net
wrote:Hi internal,
This is yet another friendly reminder from your RMs that the PHP
8.2 feature-freeze is in 2 weeks now [1]. All RFC targeting 8.2
should now be in the voting phase to respect the minimal period of
2 weeks.What time is this going to happen? If possible later than better
ofc > > so we can get more things in... :)Ah just found this https://externals.io/message/118025 so it's
2022-07-19 23:59:59 UTC which is cool! :)
I'm not sure what "more things" you want to get into 8.2 that you can
accomplish before the end of the day tomorrow. Any RFCs to be voted on
should have been opened for voting 2 weeks ago. If those votes don't
close by tomorrow, then they'll have to wait for 8.3.
Any PRs that folks want to land in 8.2 (and that don't require RFCs)
should already be opened and under review. If you open a non-trivial PR
tomorrow, hoping to land it in 8.2, you might be disappointed to find it
has to wait for 8.3.
We plan to cut the new PHP-8.2 branch tomorrow around 16:00 UTC. If
there are still PRs open that folks have already discussed and agreed
should go into 8.2, it's fine if they aren't merged yet. It'll all be
taken care of. If a vote closes tomorrow after the branch is cut, and it
passes, it will still make it into 8.2, so nothing to worry about there.
If you have a new (trivial) feature that you'd like to see in 8.2, it's
probably too late at this time, but if you want to try, go ahead and
open a PR for it. If others have time to review it before the end of the
day tomorrow, and no one thinks it's big enough to require an RFC, then
maybe it will get in to 8.2, but no promises. It all depends on folks'
availability to review.
After cutting the PHP-8.2 branch, we will set master for 8.3.0-dev. I'm
not sure yet whether 8.3 or 9.0 is coming next, so don't let this alarm
you, if you're not expecting 8.3 to be next. We'll hash out all those
details at some point later this year on the mailing list.
Cheers,
Ben