Dev Chat Summary, August 31, 2022

1. Welcome and introduction

The start of the weekly WordPress developers chat meeting in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team channel can be found at this Slack thread.

Meeting agenda preparation and facilitation: @webcommsat and @marybaum. Thanks to everyone who sent in materials or shared tickets.

Meeting summary: @webcommsat. Review: @marybaum, @costdev.

References: Contributor Handbook. Purpose and role of weekly Dev Chat, held on Wednesdays at 20:00 UTC.

2. Announcements

@bph: The GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. 14.0 is in the repo, and a Make Core post is in progress. The performance tests need another look. Props to @desrosj for getting it over the finish line and release leadRelease Lead The community member ultimately responsible for the Release. @onemaggie. Post dev chat – What’s new in Gutenberg 14.01.

3. Blogs posts

Core editor improvement: refining the template creation experience (August 25, 2022)

Post dev chat: A Week in Core (August 31, 2022) thanks to @audrasjb.

4. Upcoming releases

a) The next major is 6.1.

No specific updates from the Release Squad.
Some useful links:
6.1 development cycle
Bug scrub cycle

Other 6.1 related items:
@pbearne: is keen to get these two filters #56045 and #37930 committed. Action: @davidbaumwald is looking into this. Anyone else able to assist too?

@jeffpaul: Worth noting that BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is in less than 3 weeks and historically we’ve tried to ensure features land week prior so ideally any new features/enhancements get in by Friday, September 9, 2022.

@webcommsat: On an adminadmin (and super admin) task, the roadmap post for 6.1 does not seem to be linked from the development cycle page. Can this be added? The post also refers to a second post to follow, is this expected before Beta 1? Action: Follow-up.

@webcommsat: A question for the release leads, do we have any update on the pre-release walkthrough date? It was provisionally set for September 13, 2022.
Update Sept 1 in release leads channel: pre-release walkthrough confirmed for September 13, at 16:00 UTC. @jpantani is organizing the event via Zoom. Announcement post to follow.
Action: Add walkthrough on next week’s dev chat agenda for an update.

b) Minor releases
Key links for anyone wanting to know more about the latest minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality., 6.0.2.
WordPress 6.0.2 security and maintenance release
HelpHub page for 6.0.2

@sergeybiryukov: 6.0.2 includes 3 security fixes, 12 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. fixes for core, and 5 bug fixes for the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor. Please update if you haven’t yet.

c) Discussion on early timeframe
Core SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at discussion highlighted by @jeffpaul: What should be the definition of the early timeframe within a major release cycle?

@clorith: Noting that the early keyword is in the workflow handbook under, and since it’s aimed specifically at committers, I would presume it’s aimed at committing early.

@davidbaumwald: @jeffpaul and I had a document somewhere that was going to be the prelude to a post about defining early.

@costdev: Just throwing this in as a consideration for the Make post: we might also consider having additional keywords for specificity. e.g. needs-early-decision, etc.

@clorith: In my head, “early discussion” is “discuss as much as you want until a decision is made, if it’s still in the discussion phase, it’s not ready for milestoning”. But that’s something that would likely come out of a make post with feedback I suspect .

@jeffpaul: I think the most important bit will be the timing of what “early” means.
Action: @clorith volunteered to draft a make/core post about it to gather input, and help cement this with a proper definition. Further discussion can be added on that post.

This has a related item on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher.
Ticketticket Created for both bug reports and feature development on the bug tracker. #55603 for discussion. This issue was highlighted at a bug scrub last week. Wider feedback is requested on the approach on the ticket 2nd-opinion php82

@hellofromtonya: The above ticket is something @jrf and I will be working on following up to live working session held recently.

@hellofromtonya: Please note, WordPress Core will not be fully compatible with PHP 8.2 by the time the new PHP version is released. Handling of dynamic properties has a POC but will not be ready in time. The plan is to commit.

5. Components and tickets

Are you a component maintainer? Shepherding a ticket? Beta 1 is four weeks away, scheduled for September 20, 2022.


General: Code modernization efforts have continued on preparing WordPress core for PHP 8.2. Thanks @jrf, @antonvlasenko, @costdev, and everyone testing the PHP 8.2 PRs! Ticket #56033 for more details.


Site Health has been making strides this past week with a few tickets going in (and a few being gardened and closed as no longer relevant, or non-reproducible).

@webcommsat: Just a reminder to our other component maintainers, please do share your updates and any help you need. You can add these asynchronously to the dev chat agenda or to the Summary on the Make/ Core blogblog (versus network, site). You can also raise any tickets that you would like to highlight for help, especially if they are planned for the next release.

6. Open Floor

– Topic description core Slack channel. Action: agreed to add Dev Chat date and time.

Props to @webcommsat for the dev chat summary and @marybaum and @costdev for review, and to those who facilitated the meeting.

#6-0, #6-1, #dev-chat, #summary