Tag Archives: agenda

Benjamin Zekavica 5:03 pm on October 6, 2025
Tags: 6-9 ( 31 ), agenda, core ( 675 ), dev chat ( 856 )   

Dev Chat Agenda – October 8, 2025

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 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 📢

Call for Testing

The Test Team invites testing and feedback on two upcoming 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. 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 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.

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.

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

Benjamin Zekavica 6:22 pm on September 30, 2025
Tags: 6-9 ( 31 ), agenda, core ( 675 ), dev chat ( 856 )   

Dev Chat Agenda – October 1, 2025

The next WordPress Developers Chat will take place on Wednesday, October 1, 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.3 is now available!

This is a security release that includes two fixes. We strongly recommend updating your sites immediately. For more details, you can find the information 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.7? 

Gutenberg 21.7 is now available. The release post provides a full overview of the changes and enhancements. 

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.

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.

Splitting CSSCSS Cascading Style Sheets. class names from HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. class attribute

@dmsnell proposed #Gutenberg-PR-10043 to separate handling of CSS class names from the class attribute itself. The goal is a cleaner separation between parsing and rendering. Feedback should focus on the overall design direction, since implementation details may still change.

Refactor of wp_kses_hair()

@dmsnell is working on #63724 to align attribute parsing more closely with browsers and the HTML spec. The open question is whether attributes should be normalized (e.g., decoded, character references resolved) before being returned. This would simplify many edge cases but may introduce backward compatibility concerns.

More reliable wp_html_split()

In #Gutenberg-PR-9270, @dmsnell addresses shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. edge cases when $ignore_html = true. Legacy code treats certain sequences as tags which the HTML spec considers plain text. A decision is needed on whether Core should prioritize spec compliance or legacy compatibility.

Standard for Template Output Buffering

@westonruter raised #43258 to establish a standardized approach to output buffering in Core. Many plugins currently implement their own solutions for caching or optimization, often causing conflicts. With the new HTML 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. and DOM support in PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.4, Core could introduce a unified filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output./action structure for safe and efficient processing of the final output buffer.

Additional design feedback request

@jeffpaul highlighted Gutenberg PR #71743 and asked for design feedback.

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

Benjamin Zekavica 9:59 pm on September 23, 2025
Tags: 6-9 ( 31 ), agenda, core ( 675 ), dev chat ( 856 )   

Dev Chat Agenda – September 24, 2025

The next WordPress Developers Chat will take place on Wednesday, September 24, 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 📢

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. Meeting notes from 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 2025

Notes from the Core Committer meeting at WCUS 2025 are now available.

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.

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 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.

UTF-8 Support / mbstring

@dmsnell Work on UTF-8 support continues with a notable change in #9498: functions are now conditionally defined based on the presence of the mbstring extension.

Core Importer Feedback / Maintainer

@zodiac1978 raised in #core-program that the Core Importer team currently has no component maintainer and needs feedback. Two open questions:

  • How do we get more eyes on that 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/. channel and repo?
  • How do we get collaborators or maintainers involved?

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

Benjamin Zekavica 5:07 pm on September 16, 2025
Tags: 6-9 ( 31 ), agenda, core ( 675 ), dev chat ( 856 )   

Dev Chat Agenda – September 17, 2025

The next WordPress Developers Chat will take place on Wednesday, September 17, 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 📢

Welcome to the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Program Team

The new Core Program Team focuses on how Core’s sub-teams work together. The goal is to make processes simpler, lower barriers for new contributors, and support smoother collaboration—for example through new handbooks or 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/ project flows. Everyone’s welcome to get involved.

Help Test WordPress 6.9

@krupa and @psykro are preparing the Help Test WordPress 6.9 post. They’re asking for input on which features need a dedicated testing call, what should be tested early before 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, and which workflows may need extra coverage.

Forthcoming releases 🚀

WordPress 6.9 Timeline

WordPress 6.9 is planned for December 2, 2025, with Beta 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 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.

REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. Sites Endpoints

@realloc suggests revisiting the inactive wp-api-sites-endpoints repo, originally meant for Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site REST API work, to discuss how this could be restarted as part of modernizing Networknetwork (versus site, blog) Adminadmin (and super admin).

Onboarding with WPCredits

@devmuhib notes that the WPCredits initiative is now used in universities, bringing new contributors into Core. Discussion will look at how to make onboarding simple and effective.

Strong Typing in Core

@SirLouen raises the question of how type hints should be handled in WordPress, since they are being introduced inconsistently. Input is welcome, with ticket #63975 as a reference.

Component Maintainer Request: Post/Post Types

@sirlouen is requesting to join as Component Maintainer for Post/Post Types.

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.

Thanks to @francina for reviewing this agenda.

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

Jb Audras 8:29 pm on September 9, 2025
Tags: 6-9 ( 31 ), agenda, core ( 675 ), dev chat ( 856 )   

Dev Chat Agenda – September 10, 2025

The next WordPress Developers Chat will take place on Wednesday, September 10, 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 📢

Forthcoming releases 🚀

WordPress 6.9

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

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.

WP 6.9 Dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.:

  • A first 6.9 dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. was published: Prettier Emails: Supporting Inline Embedded Images

See all dev notes published for 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.

  • @mindctrl wants to discuss ticket #5276 and the possibility to include this pretty old ticket to milestone 6.9.
  • @anonymooo proposes to discuss ticket #63678.

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

Benjamin Zekavica 5:20 pm on September 2, 2025
Tags: 6-9 ( 31 ), agenda, core ( 675 ), dev chat ( 856 )   

Dev Chat Agenda – September 3, 2025

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

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.5 was released!

Gutenberg 21.5 is now available. The release post provides a full overview of the changes and enhancements. Thanks to @wildworks for leading this release and preparing the notes.

What’s new in Gutenberg 21.5? (27 August)

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.

Networknetwork (versus site, blog) Adminadmin (and super admin) “Sites” revamp with DataViews/DataForm

@realloc started #63885 during WCUS, proposing a revamp of the Network/Sites screen using DataViews and DataForm. He would like to gather feedback and hear different opinions on the approach during the chat.

PHPStan in Core Development Workflow

@justlevine would like to discuss next steps on the proposal to integrate PHPStan into the WordPress core development workflow and #61175. The focus will be on collecting feedback and exploring a path forward for introducing static analysis into Core’s tooling.

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.

Props to @francina for review.

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

Benjamin Zekavica 8:50 am on August 26, 2025
Tags: 6-9 ( 31 ), agenda, core ( 675 ), dev chat ( 856 )   

Dev Chat Agenda – August 27, 2025

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

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 2025 takes place this week

From August 26–29, 2025, the WordPress community will convene in Portland, Oregon.
Further details can be found on the official website.

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.

Forthcoming releases 🚀

Next 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/ version: 21.5

Gutenberg 21.5 is scheduled for release on Wednesday, August 27, 2025.

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.

Post/Post Types Bug Scrubs

@sirlouen announced he will start running weekly 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. scrubs beginning in September, every Thursday at 1 PM GMT. The focus will be on the Post/Post Types component, and the effort is expected to continue for an extended period (possibly into 2026). He suggested permanently adding this as a recurring event in the meeting calendar.

New Database Index Proposal

@josephscott proposed adding a new database index to improve performance on sites with a large number of posts or custom post types. The index would be:

CREATE INDEX type_status_author ON wp_posts (post_type, post_status, post_author);

This change would speed up queries for the All Posts adminadmin (and super admin) page. Details are in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket #50161, comment 7. A discussion is requested on whether this index should be included in Core.

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

Benjamin Zekavica 6:16 pm on August 19, 2025
Tags: 6-9 ( 31 ), agenda, core ( 675 ), dev chat ( 856 )   

Dev Chat Agenda – August 20, 2025

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

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 2025 is coming up next week

From August 26–29, 2025, the WordPress community will gather in Portland, Oregon for this year’s WordCamp US. If you haven’t already, be sure to register for the Contributor Day. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team members will be on site, and it would be great to see you there as well.

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.4?

The latest version of Gutenberg, 21.4, was released on August 13. For a detailed overview of what has changed, check out the article What’s new in Gutenberg 21.4? – many thanks to @priethor for putting together this excellent summary.

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.

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 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.

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. Pattern Registration – Silent Failures

@tusharbharti reported that register_block_pattern() currently returns true even when disallowed blocks are included. As a result, the pattern doesn’t appear in the inserter and no warning is shown. He has opened TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket #63765 and submitted 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. (PR#9345). A second opinion is requested.

MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. Rate Limiting – Redirect Issue

@anonymooo highlighted ticket #63678, where WordPress incorrectly redirects to wp-admin/install.php when a user is rate-limited in MySQL. An associated (PR#9223) is open and still needs review.

Bug Scrubbing Announcements

@sirlouen would like to continue his 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. scrubbing activities as a new component maintainer. He’s requesting permission to post his own announcements in the #core channel to plan independently. His next scrub is scheduled for Monday, August 25, 2 PM GMT.

UTF-8 Handling Improvements

@dmsnell suggested updating wp_check_invalid_utf8() (ticket #63837) following the earlier work on seems_utf8()(ticket #38044). The goal is to improve UTF-8 validation. Community feedback is invited before changes move forward.

Data Passing in Scripts

@jonsurrell, in discussion with @westonruter, raised the idea of adapting the data passing mechanism from Script Modules for classic scripts. Benefits include better performance, no execution on load, and no reliance on a global namespace. This could provide an alternative to wp_add_inline_script() and wp_localize_script(). Feedback is welcome.

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

Jb Audras 7:30 am on August 13, 2025
Tags: 6-9 ( 31 ), agenda, dev chat ( 856 )   

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

Jb Audras 11:18 pm on August 5, 2025
Tags: 6-9 ( 31 ), agenda, dev chat ( 856 )   

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