The next WordPress Developers Chat will take place on Wednesday, October 8, 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 ticket 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.
Announcements 📢
Call for Testing
The Test Team invites testing and feedback on two upcoming block 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 features:
The linked posts include detailed instructions on how to test, how the features behave in the editor, and how to report any issues.
Forthcoming releases 🚀
WordPress 6.9 Timeline
WordPress 6.9 is planned for December 2, 2025, with Beta 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.
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 Core 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.
Improving error handling (wp_die()
replacements)
@callumbw95 opened ticket #64009, which proposes reviewing and updating existing wp_die()
calls that currently result in 500 errors. The goal is to establish a more consistent approach to error handling and reduce unnecessary error entries in logs.
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
You must be logged in to post a comment.