Weekly Core Meeting - 2023-07-06

[viktor]

View in #core on Slack

@Viktor: Anyone around for the meeting this week?

@Matt_Robinson: I’m here but can’t stay for the full meeting, I have maybe 15 minutes this week.

@Viktor: I think that’s enough, we don’t have much to discuss.

@Matt_Robinson: Here is a summary of the changes I have noted over the last week:
• In the past week the API endpoint for v2 has been updated to indicate PHP > 7.4 is required.
• Renovate updates have been merged as needed.
• PHP 8.1 testing is now fully enabled and required before merging
• The media modal fixes are merged, as is a fix for default sender details from wp_mail()
• A fix has been applied to grunt-contrib-qunit after I raised an issue based on our testing that has removed the issue seen in tests with QUnit undefined displayed in the passing tests
We may need to increase timeout for QUnit testing due to observed issues from time to time in the automated testing

@Viktor: Great work. I started testing v2 in PHP 8.1 last week. So far so good.
On my end, I will have a bit more time next week and I will try to get documentation links PR submitted for testing. Part of the problem is that docs URLs need to be updated, too. I don’t want v2 to have old URLs.

@Matt_Robinson: I think we are maybe getting close to a release candidate for v2 then. For v1 we need to make a 1.6.0 release with the upgrade notice and deprecation warning for PHP < 7.4 that is implemented in v2 so could do with a wording review there.
Some issues need closed off as either complete in v2, not happening now with current developer time pressures or deprioritised / plugin area perhaps.

@Viktor: Yes, I will most likely have time to submit feedback on the 1.6.0 notice PR tomorrow. So we can get 1.6.0 RC out next week.
For the issues in the v1 repo, I did go through some. But you’re welcome to close any you think should be closed.

@Matt_Robinson: I’ll have a look if I get some spare time. Anything else for this week?

@Viktor: I think that covers it for this week.

@Matt_Robinson: Thanks