Dev Chat Agenda – October 15, 2025

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.

The next WordPress Developers Chat will take place on Wednesday, October 15, 2025, at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

The various curated agenda sections below refer to additional items. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.

Forthcoming releases 🚀

WordPress 6.9 Timeline

WordPress 6.9 is planned for December 2, 2025, with 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 beginning October 21. Join one of the release parties to make WordPress.

Bug Scrub Schedule

Regular scrubs are already underway, led by @wildworks and @welcher across time zones.
Full details are in the Bug Scrub Schedule for WordPress 6.9.

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

@luminuu asked for a final review of https://github.com/WordPress/gutenberg/pull/71703. There’s one issue with some failing tests, but while the tests indicate that something isn’t imported, it is actually present in the file. If anyone has any idea, I’d appreciate the feedback. Jessica made all the requested code changes and would like to get the ticket in for 6.9, as it resolves a poor user experience for anyone trying to use font size presets, especially when using fluid custom values.

@westonruter asked for a final review of https://github.com/WordPress/wordpress-develop/pull/8412

@gziolo would like to clarify the process for including Abilities in WP 6.9 (See Slack thread).

Open floor 🎙️

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.

#6-9, #agenda, #core, #dev-chat

Dennis Snell 4:35 am on October 15, 2025

After considerable changes to the designed interface, WP_Block_Scanner is ready for final review.

This class introduces a streaming low-overhead method for processing 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. documents in a similar way to how the HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. is designed to process HTML.

It has undergone a lot of change over the past few months and the PR links to a couple of example refactors with potential for a large performance payoff, particularly when trying to extract a portion of a block within a larger document.

wordpress/wordpress-develop#9105 — Core-61401
Dennis Snell 4:41 am on October 15, 2025

There’s an old discussion about PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher’s deprecation of utf8_encode() and utf8_decode(). Recent work on UTF-8 support has made it easier today to conditionally provide polyfills for those functions, polyfills which include appropriate deprecation notices for developers.

It would be nice to see some new thoughts on this since it was last active 18 months ago. There are additional concerns in the ticketticket Created for both bug reports and feature development on the bug tracker. for CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. work, but a polyfill in Core can alleviate a number of concerns with the coming changes to PHP while preventing sites from crashing.

wordpress/wordpress-develop#10011 — Core-55603
Cory Hughart 1:58 pm on October 15, 2025

The Terms Query 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. effort needs more feedback on the main issue and a few PRs to maybe stabilize the block for 6.9, mainly summarized by this comment: https://github.com/WordPress/gutenberg/issues/49094#issuecomment-3402959782

The most important PRs in particular are:

Feature enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature., selected terms: https://github.com/WordPress/gutenberg/pull/72286

Update inherit control: https://github.com/WordPress/gutenberg/pull/72313

Welcome!

Communication

Forthcoming releases 🚀

WordPress 6.9 Timeline

Bug Scrub Schedule

Discussions 💬

Open floor 🎙️

Share this:

Site resources