On Mon, Sep 28, 2020 at 10:56 AM Gabriel Caruso <carusogabr...@php.net> wrote:
> Following Sara's email a couple of weeks ago, I come this week with a > similar one: > > Next Tuesday, Sep 29th, has been marked on our calendars as the branch date > for PHP-8.0 which would open master up for 8.1 targeted work. > > This would mean that bug fixes would need to include PHP-8.0 in their merge > chain (meaning more work to merge 8.0 targeted fixes). > > Please let Sara and I know how you feel about this date. We can see that > master is still quite active, especially with > https://github.com/php/php-tasks/issues/18 and > https://github.com/php/php-tasks/issues/16, and we don't wish to make the > work to stabilize > the 8.0 release any more difficult than it has to be. > Current status: The warning promotion is essentially complete. On https://github.com/php/php-tasks/issues/18 everything is ticked or has a PR that will land by tomorrow. The parameter name review however is still very much work in progress: https://github.com/php/php-tasks/issues/23 This is going slower than anticipated, in part because parameter names are prime bikeshedding material, so it can take a while to reach consensus. In the last thread, Dmitry mentioned that he wanted to merge the JIT and VM helpers. I don't believe that has happened, but also don't know what the plans there are. Regarding the branch cut, I think we can either: 1. Cut the branch tomorrow, freeze ABI and release RC1, but continue with the parameter name review afterwards. 2. Delay RC1 again. I'd probably go for 2. to avoid the extra merges for another two weeks -- as you said, activity targeting 8.0 is still rather high. Regards, Nikita
