Dev chat summary, June 29, 2022

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

@marybaum led the meeting on this agenda.

For your records, last week’s summary came from @chanthaboune.

Announcements

@craigfrancis gave a big shoutout to the folx who helped him on tickey #52506, which will likely be ready to land in 6.1. (TL;dr it’s a much-needed database-access improvement).

Blogblog (versus network, site) posts of note

A Week in Core from @audrasjb

A call for testing from @afragen

And two reposts from @chanthaboune‘s summary:

There’s a discussion about how to update the wp-admin experience.

There’s a discussion on Yoda conditions (which started in the WPCS repo)

Upcoming releases

The next major is 6.1.

@bph shared @priethor‘s 6.1 planning roundup. Leave a comment there if you’d like to volunteer!

Birgit also shared this report. The current schedule, which is not confirmed, shows feature freeze is September 20, roughly eleven weeks from now.

There was some discussion.

The next minor is 6.0.1.

Here’s the plan!

Open floor

@craigfrancis asked for eyes on #54042 (PR:2191).

@sergey reported on his components.

Build/test tools:
- #55652 updates npm and other dependencies to their latest versions.
- #39265 continues progress on adding missing `@covers` tags for the WordPress unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. suite.
General: #56009 and #56033 are starting the process of modernizing code to support PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.2.

On those tickets, Sergey thanked @desrosj, @jrf, @azaozz, @pbearne, @hellofromtonya, @antonvlasenko, @ironprogrammer, and @costdev.

@sabernhardt announced that a special `good-first-bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.` scrub will start today at 21:00 UTC, right after the usual weekly 6.1 scrub.

And @afragen would like help testing his feature plugin that’s all about plugin dependencies. More details are here.

#core, #dev-chat, #summary