The WordPress coreCoreCore 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 bugbugA 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.
It’s time to get WordPress 6.9 ready for release, and help is needed to ensure it’s smooth and bugbugA 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.-free. Whether you’re an experienced contributor or joining in for the first time, everyone is welcome! 🎉
Schedule Overview
Regular bug scrubs are being held twice a week with @wildworks and @welcher leading them in their individual timezones. The goal is to cover as many timezones as possible to encourage as many contributors as possible to participate in the 6.9 release. As the release date approaches and activity ramps up, the number of scrubs may be increased if necessary. These efforts will help ensure everything is on track for a smooth launch. Participation is welcome at any of these sessions, so feel free to join. Bring questions, ideas, and let’s scrub some bugs together!
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 ticketticketCreated 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 blockBlockBlock 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 discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the CoreCoreCore 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 PHPPHPThe 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 standardsWordPress Coding StandardsThe 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.
The current WordPress Coding Standard does not specify which file extensions should be used for PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher files. This proposal establishes that only the .php file extension should be allowed for PHP files.
Motivation
While web servers like ApacheApacheApache is the most widely used web server software. Developed and maintained by Apache Software Foundation. Apache is an Open Source software available for free. and NginxNGINXNGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. https://www.nginx.com/. can be configured to execute files with various extensions as PHP (e.g., .php3 and .phtml), the .php extension is the only one universally supported. If PHP files do not use the .php extension, there is a risk that scripts will not work on some web servers. For example, a default Debian installation using Apache and mod_php parses .php, .phtml, and .phar as PHP, whereas a default Fedora installation using Apache and mod_php parses only .php and .phar as PHP. This means that a pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party using .phtml file extensions will work on Debian, but not on Fedora (and may inadvertently render code in plain text). Therefore, for code portability, compatibility, and security, it should be agreed and checkable that only .php extensions are used for PHP files.
Another benefit of the change proposed here is that if all PHP files use the .php extension, we can be sure that they will be checked by tools like PHPCSPHP Code SnifferPHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS..
WordPress 6.9 BetaBetaA 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 now available!
The Test Team invites testing and feedback on the following upcoming blockBlockBlock 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:
Several contributors shared feedback on the Beta 1 preparation and suggested writing down the key points for later review. Topics mentioned included how build failures are handled in relation to the schedule, when to apply freezes, adding more time to stabilize changes before milestones, and syncing the codebases more often to keep the process smooth.
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 ticketticketCreated 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 BetaBetaA 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 now available!
WordPress 6.9 Beta 1 is now available for download and testing. Further information you can find here. The final release is currently scheduled for December 2, 2025.
Call for Testing
The Test Team invites testing and feedback on the following upcoming blockBlockBlock 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 discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the CoreCoreCore 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.
No topics have been submitted for the discussion round yet. If you have something in mind, feel free to write it in the comments 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.
WordPress 6.9 BetaBetaA 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 ready for download and testing!
This beta release is intended for testing and development only. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, use a test environment or local site to explore the new features.
How to Test WordPress 6.9 Beta 1
You can test WordPress 6.9 Beta 1 in any of the following ways:
WordPress Beta Tester PluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party
Install and activate the WordPress Beta Tester plugin on a WordPress install. Select the “Bleeding edgebleeding edgeThe latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “Beta/RCrelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). Only” stream.
Command Line (WP-CLIWP-CLIWP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/https://make.wordpress.org/cli/)
Use this WP-CLI command: wp core update --version=6.9-beta1
The scheduled final release date for WordPress 6.9 is December 2, 2025. The full release schedule can be found here. Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Thank you to everyone who contributes by testing!
How important is your testing?
Testing for issues is a critical part of developing any software, and it’s a meaningful way for anyone to contribute—whether or not you have experience. Details on what to test in WordPress 6.9 are here.
If you encounter an issue, please share it in the Alpha/Beta area of the support forums. If you are comfortable submitting a reproducible bugbugA 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. report, you can do so via WordPress Trac. You can also check your issue against this list of known bugs.
WordPress 6.9 will include many new features that were previously only available in the GutenbergGutenbergThe 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. https://wordpress.org/gutenberg/ plugin. Learn more about Gutenberg updates since WordPress 6.8 in the What’s New in Gutenberg posts for versions 20.4 & 20.5, 20.6 & 20.7,20.8 & 20.9,21,21.1,21.2, 21.3, 21.4, 21.5,21.6, 21.7, 21.8 & 21.9
What’s new in WordPress 6.9?
This release brings major advancements in editing, collaboration, and developer capabilities.
Site Editor
Expanded Template Management: Create multiple templates per slug, draft before publishing, activate or deactivate templates as needed, and retain custom templates when switching themes.
Content Creation & Editor Features
Notes: Notes can now be attached to individual blocks. This enables asynchronous collaboration and more efficient editorial workflows. This was formerly known as ‘BlockBlockBlock 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. Comments’.
Hide Blocks on Frontend: You can hide blocks from the frontend while leaving them editable in the backend—supporting staging, alternate design explorations, and non-destructive workflows.
New Blocks: Accordion, Terms Query, Math block and Time to Read. The ‘Fit text’ formatting option is now available for paragraph and heading blocks, providing more flexibility for site building.
Drag and drop block experience: Instead of dragging a copy, users now move the actual block itself within the editor while rearranging content. The result is a visually enhanced and accessible editing experience for all users
Command Palette
Command Palette (Press Ctrl+K or Command+K anywhere in the dashboard to use the command palette) is available across both the Editor and the Dashboard, making navigation and actions faster and easier. Simply type in the Command Palette to search, jump to specific screens, or trigger actions directly. This also lays the groundwork for future integrations with the new Abilities APIAPIAn 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..
Developer & API Updates
New Abilities API: A unified registry of callable WordPress capabilities with defined inputs and outputs, built for AI integrations and developer automation.
Interactivity API Improvements: A new algorithm powers client-side navigation, enabling developers to build new user experiences that weren’t possible before and will be included in future WordPress versions, like instant search or client-side comment submissions.
DataViews & DataForm components: The release introduces support for more field types & new layouts. DataViews now offers infinite scroll for large datasets and allows for locked filters and improved multi-selection via the new DataViewsPicker.
HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. API: These upgrades make parsing, transforming, and validating HTML safer and more efficient across blocks, site editor, and custom plugins, boosting programmatic HTML manipulation accuracy.
Block Binding API: Date block supports block bindings, image block allows binding the caption, an improved and extensibleExtensibleThis is the ability to add additional functionality to the code. Plugins extend the WordPress core software. user interface that allows custom sources in the bindings editor.
Performance
Introduced the “template enhancementenhancementEnhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. output buffer” to unlock new optimization opportunities.
Block styles loaded on demand in classic themes to reduce overall CSSCSSCascading Style Sheets. used.
Support for fetchpriority on scripts and script modules.
Support for printing script modules in the footer.
Increased inlining of stylesheets to reduce render blocking.
Minification of stylesheets in coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. block themes.
Scripts and styles for hidden blocks omitted by default.
Emoji detection script converted to a script module and moved to footer.
Database query optimizations and caching.
Cron spawned at shutdown instead of init to reduce impact on TTFB.
Improvements to RSS feedRSS FeedRSS is an acronym for Real Simple Syndication which is a type of web feed which allows users to access updates to online content in a standardized, computer-readable format. This is the feed. caching.
UTF-8 processing optimizations.
Additional Notes
No new default theme in 6.9: There is no bundled theme shipping with 6.9; the focus is on enhancing the editor experience, API support and performance.
Early Preview Plugins: MCP Adapter, and PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher AI Client are launching as canonical packages and plugins alongside 6.9, but are not part of Core.
The MCP Adaptor turns WordPress Abilities into MCP Tools that can be used by AI agents.
The PHP AI Client allows WordPress to connect to LLMS for AI powered content creation.
Just for you: a Beta 1 haiku
Beta moon arises, In its glow, we debug dreams— Stable stars ahead.
CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. is currently in the WordPress 6.9 release cycle. There are now less than six days until betaBetaA 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 on 21 October!
No maintenance release is currently being planned. If anyone has an issue they think would require a maintenance release, you are encouraged to discuss it in the #6-8-release-leads channel.
Next GutenbergGutenbergThe 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. https://wordpress.org/gutenberg/ release: 21.9
Gutenberg 21.9 RCrelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). was pushed back to Friday. More Info in this slack thread
Call for Testing
The Test Team invites testing and feedback on the following upcoming blockBlockBlock 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 two specific pieces that could use some help here are:
Feature enhancementenhancementEnhancements 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
Merging the Abilities APIAPIAn 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.
The Feature Plugin Merge Criteria were reviewed and as this was never published as a pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (only a composer package), it’s not necessary to deactivate it when it is merged into core.
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 ticketticketCreated 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 BetaBetaA 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.
The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the CoreCoreCore 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.
@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.