On Tue, 19 Jul 2022, 02:57 Ben Ramsey, <ram...@php.net> wrote: > This was a continuation of a previous thread, but I felt my notes below > warranted splitting off into a new thread. > > On Mon, Jul 18, 2022 at 18:02 Jakub Zelenka <bu...@php.net> wrote: > > > On Mon, Jul 18, 2022 at 11:59 PM Jakub Zelenka <bu...@php.net> wrote: > > > > > Hi > > > > > > On Tue, Jul 5, 2022 at 7:09 PM Pierrick Charron <pierr...@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. >
You can just filter 8.2 milestone in GitHub and you will see that there are still some PR's that are almost ready and can be merged possibly with just a few tweaks. I merged some yesterday but there are more. > 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. > I think this is not how it was done for previous version branches. I think we created them when it got to RC stage. Any new features are on hold and we (core devs) should mainly concentrate on bugs during beta. I would prefer if it could stay that way as it reduces time of merging things. >
