The next WordPress Developers Chat will take place on Wednesday, October 29, 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.
Forthcoming releases 🚀
Call for Testing
The Test Team invites testing and feedback on the following 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:
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.
Coding Standard Proposal: Make it explicit that PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher files must use the .php extension
The current WordPress coding standards The Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook.
May also refer to The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the PHP coding standards. do not define which file extension should be used for PHP files. This proposal recommends standardizing on the .php extension exclusively. @rodrigosprimo has published a detailed post outlining the rationale.
No further topics have been submitted for this discussion round yet.
If you have something in mind, feel free to leave a comment below this post.
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
