Dev Chat Agenda – August 13, 2025

The next WordPress Developers Chat will take place on Wednesday, August 13, 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.

Announcements 📢

WordPress 6.9 Roadmap

The roadmap for 6.9 has been published. Please take a look to see what’s actively being worked on for release later in the year.

WordPress 6.9 Planning Proposal and Call for Volunteers

The planning phase for 6.9 wrapped up on July 25. More information will be announced about the release team in the coming weeks.

Forthcoming releases 🚀

WordPress 6.9

WordPress 6.9 is scheduled for Tuesday, December 2, 2025.

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.

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, #dev-chat

Dev Chat Agenda – August 6, 2025

The next WordPress Developers Chat will take place on Wednesday, August 6, 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.

Announcements 📢

WordPress 6.9 Roadmap

The roadmap for 6.9 has been published. Please take a look to see what’s actively being worked on for release later in the year.

WordPress 6.9 Planning Proposal and Call for Volunteers

The planning phase for 6.9 wrapped up on July 25. More information will be announced about the release team in the coming weeks.

Maintenance release for WP 4.7 to 6.7

A maintenance update was released for branches 4.7 to 6.7.

Forthcoming releases 🚀

WordPress 6.9

WordPress 6.9 is scheduled for Tuesday, December 2, 2025.

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.

“New blocks in core” guidelines (and their lack of)

Pointed out by @mamaduka: “Do niche blocks belong in the core?”. See the related issue on Gutenberg GitHub repository.

Request for comments on a new 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. system for processing blocks

@dmsnell proposed to discuss this PR proposal.

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, #dev-chat

Dev Chat Agenda – July 30, 2025

The next WordPress Developers Chat will take place on Wednesday, July 30, 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.

Announcements 📢

WordPress 6.9 Roadmap

The roadmap for 6.9 has been published. Please take a look to see what’s actively being worked on for release later in the year.

WordPress 6.9 Planning Proposal and Call for Volunteers

The planning phase for 6.9 wrapped up on July 25. More information will be announced about the release team in the coming weeks.

Forthcoming releases 🚀

WordPress 6.9

WordPress 6.9 is scheduled for Tuesday, December 2, 2025.

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. https://wordpress.org/gutenberg/ 21.3

The Gutenberg 21.3 release is scheduled for Wednesday, July 30. RC1 was released on July 28, and RC2 was released on July 29. Props to @wildworks for handling this release ✨

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.

Posts without titles cannot be saved when all content is removed

This is an open issue discussing how to handle saving posts without titles, as they can’t be saved when all content is removed from the post. They need to have at least one 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. to be saveable. @mediaformat mentioned that it has a stale patch, but they have documented an additional use case related to the block bindings 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..

Make seems_utf8() RFC 3629 compliant

@dmsnell raised Core-38044, which while not huge, could be a nice addition to 6.9.

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.

Thank you to @jorbin for reviewing.

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

Dev Chat Agenda – July 23, 2025

The next WordPress Developers Chat will take place on Wednesday, July 23, 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.

Announcements 📢

WordPress 6.9 Planning Proposal and Call for Volunteers

The planning phase for Release 6.9 is now underway.
Applications for the various roles should be submitted here.

What’s new in 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. https://wordpress.org/gutenberg/ 21.2?

@priethor published a detailed post about the release of Gutenberg pluginPlugin A 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 version 21.2. There you’ll find a comprehensive overview of all the changes and new features introduced in this version.

Forthcoming releases 🚀

WordPress 6.9

WordPress 6.9 is scheduled on Tuesday, December 2, 2025.

Gutenberg 21.3

The release of Gutenberg 21.3 is scheduled for Wednesday, July 30.

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.

Proposal to Include PHPStan in WordPress 6.9

The proposal to introduce PHPStan as a static analysis tool in WordPress 6.9 is ready for further discussion. The goal is to determine whether and how PHPStan can be integrated into the core workflow. Key open points and areas requiring input are outlined in #61175.

Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in Media Playlist – Ticket #63583

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. affecting media playlists has been reported in Trac ticket #63583. The issue has been successfully reproduced and a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. is already available. @rollybueno has asked whether the ticket can be assigned to a milestone so that progress can continue.

Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. Table Leads Needed for WCUS 2025

We need to discuss who from the Core Team will be available on-site at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US to serve as table lead or assist with onboarding and coordination during Contributor Day on August 26. Confirmation is needed by July 25.

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, #dev-chat

Dev Chat Agenda – July 16, 2025

The next WordPress Developers Chat will take place on Wednesday, July 16, 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.

Announcements 📢

WordPress 6.8.2 is now available!

The WordPress 6.8.2 is now available! A heartfelt thank you to everyone who joined the Release Party. We appreciate your testing and feedback.

WordPress 6.9 Planning Proposal and Call for Volunteers

The planning phase for Release 6.9 is now underway.
Applications for the various roles should be submitted here.

Forthcoming releases 🚀

WordPress 6.9 is scheduled on Tuesday, December 2, 2025.

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.

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.–Based kses Parsing

#63694 and #63630  Brief review of PR #9256 and PR #9099: assess replacing wp_kses_hair() ad-hoc parsing with the HTML API, validate compatibility, performance, and security, and define a test and rollout strategy.

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, #dev-chat

Dev Chat Agenda – July 9, 2025

The next WordPress Developers Chat will take place on Wednesday, July 9, 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.8.2 RC1 is scheduled on Tuesday 8, 2025.

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.

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-8-2-2, #agenda, #dev-chat

Dev Chat Agenda – July 2, 2025

The next WordPress Developers Chat will take place on Wednesday, July 2, 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.

Announcements 📢

Highlighted Post

Proposal: Clarifying Core’s Database Support Policy

Forthcoming releases 🚀

WordPress 6.8.2 is underway.

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.

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-8, #agenda, #dev-chat, #wceu-25

Dev Chat Agenda – June 25, 2025

The next WordPress Developers Chat will take place on Wednesday June 25, 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.

Announcements 📢

None for this week

Forthcoming releases 🚀

WordPress 6.8.2 is underway.

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.

  • Brainstorming suggested by @paaljoachim “The Full Site Editor is fairly new and there are naturally features that could be improved. It would be great with an overview of current FSE plugins that aim to improve what we have today. I find it difficult to locate external FSE plugins. How can be make FSE plugins more visible in the repo?
    This could perhaps also be extended to walk through the current 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. https://wordpress.org/gutenberg/ pluginPlugin A 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 -> experiments and where these currently are at in their development phase.”

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-8, #agenda, #dev-chat, #wceu-25

Dev Chat Agenda – June 18, 2025

The next WordPress Developers Chat will take place on Wednesday June 18, 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.8.2 and beyond

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.

  • The following tickets were mentioned by Will Garcia on Slack. They asked whether these tickets are likely to be fixed, since the related dependencies are frequently pointed out as outdated by security compliance audits:
  • Mentioned by @justlevine:
    • Concerning  #61175 (Integrate PHPStan into the core development workflow): “We still to have a serious look at what PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher Static Analysis errors we want to ignore (e.g. bc they conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. with WPCSWordPress Community Support A public benefit corporation and a subsidiary of the WordPress Foundation, established in 2016., should be handled in a follow-up after the tool is merged, etc) vs baselined (enforced on new code, but not justifiable enough on it’s own to the required criteria for a code refactor).”
      For more info on this topic, see this thread in the #core-coding-standards channel.
    • Also they pointed out that “there’s some PHPStan Level 0 +1 errors that I need help remediating (if we dont baseline/ignore them in the previous bullet) […] If anyone else is interested in lending a hand here, please chime in on the ticket, in chat, or via DM”.
  • @sirlouen mentioned: as per Monday’s 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. scrub there are two tickets that need to discussed about errors in Direct Execution of Files. See tickets #62722 and #63316. The discussion should go around if this kind of issues should be covered or is not something of priority for WP.
  • Finally, @krupajnanda proposed the following: “I’d love to discuss some pointers shared in the recent WCEU Core Committers notes, especially around improving the quality and timing of testing, reviving structured user testing, and making better use of tools like the 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. pluginPlugin A 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. Looking forward to some guidance and input on how test team can align better with the Core team’s needs.”

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-8, #6-8-2-2, #agenda, #dev-chat, #wceu-25

Dev Chat Agenda – June 11, 2025

The next WordPress Developers Chat will take place on Wednesday June 11, 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.8.2 and beyond

  • The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases. A release squad for 6.8.2 and 6.8.3 will be announced soon.

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core 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.

TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. Tickets

Misc Topics

Bottlenecks when publishing posts. Mentioned by @justlevine in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. Proposed solutions:

  • Create a list of reviewers with publishing privileges so an author knows who to contact to move things forward once the post has been peer-reviewed.
  • Create a list of volunteer authors who can help with drafts. For example: 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. https://wordpress.org/gutenberg/ Release Manager could fulfil their responsibility by tagging those volunteers.
  • Create a GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ action from wordpress/gutenberg that triggers a Slack message to Core on Gutenberg release.
    • This solution can also automate a message about rc1 in Slack tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) volunteers in #core-editor 

@jorbin replied that there might be consent issues and it’s also hard to predict who is active on a day in/day out basis. Starting from a message in #core or #core-editor for someone with publish permissions to review and publish could be enough.

To be discussed 🙂

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-8, #6-8-3, #agenda, #dev-chat, #trac, #wceu-25