Tag Archives: summary

Birgit Pauli-Haack 1:58 pm on November 11, 2025
Tags: , , , summary   

Developer Blog editorial meeting notes of November 6, 2025

Summary of the WordPress Developer Blogblog (versus network, site) meeting, which took place in the  #core-dev-blog channel on the Make WordPress 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/.. Start of the meeting in Slack.

Attendees: @areziaal, @greenshady, @psykro, @marybaum, @flexseth, @bcworkz (async), @webcommsat (async) and @bph (facilitator).

Last meeting notes: Dev Blog editorial meeting summary, October 2, 2025

Updates on the site

The workflow for notification on the What’s new for developers round-up issue: A second notification 20 days after the issue is created to remind people about the deadline of the 5th of the month.

It’s time to make Snippets a first class content now that we have five snippets published and more in the queue. For this month, I plan to update the archive template and add Snippets to the navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site.. (This was done: Snippets)

Newly published posts since last meeting

Huge thank you to the writer and reviewers! 🎉👏

Project status

The project board for Developer Blog content is on 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/.

We have approved topics that still require a writer:

If you know someone who could tackle any of those topics, please comment on the particular issue.

New topics approved

Open Floor

Discussing the Google Docs template with @flexseth, it turns out not everyone can add a Code 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 a Google Doc. It seems to be reserved for Workspace account. To work around this restrictions, writers can copy/paste the code block from the template and modify it to their needs.(Slack convo)

Upcoming meetings

  • 📣 Last meeting 2025: December 4, 2025, at 15:00 UTC
  • 📢 First meeting in 2026: January 8, 2025, at 15:00 UTC

Both happening in the #core-dev-blog channel

Props to @areziaal for review.

#dev-blog

#meeting, #summary

Aditya Dhade 7:03 pm on October 7, 2025
Tags: , , , , summary   

Performance Chat Summary: 7 October 2025

The full chat log is available beginning here on Slack.

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

  • @westonruter mentioned ticketticket Created for both bug reports and feature development on the bug tracker. #63636 related to BFCache was punted due to an unresolved Chromium 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. around Clear-Site-Data: "cache" headers.
  • @westonruter identified ticket #43258 on output buffering as the current biggest blockerblocker A bug which is so severe that it blocks a release.. He explained that while there’s been significant discussion both on the PR #8412 and in Slack, the debate centers around the trade-offs between enabling full-page buffering (to allow post-render optimization) versus keeping the door open for streaming, which could improve initial load performance. He provided further context on how classic themes already stream via procedural rendering, while 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. themes generally do not.
    • @westonruter noted that while streaming isn’t widely adopted in WordPress today, it could become valuable in the future, and care should be taken not to block its evolution. He also shared a WPDirectory search of flush() usage across coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., noting they appear mostly in adminadmin (and super admin) and XML-RPC contexts rather than template rendering.
    • @westonruter asked if anyone has insights into this area and can contribute thoughts on how we can bridge these two perspectives, allowing for a default output buffer while also enabling streaming if the application wants it. He’d be most thankful.
  • @b1ink0 brought up PR #9867 related to footer script module support and noted that @jonsurrell had provided thoughts around dependency handling.

Performance Lab 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 (and other performance plugins)

  • @westonruter mentioned new guidance on AI-generated contributions now available in the Performance repo, including a new AGENTS.md file and updated PR template instructions with PR #2193. He explained that this was prompted by a recent increase in AI-assisted PRs, some of which indicated the AI’s output wasn’t being carefully reviewed by the contributor.

Open Floor

  • @westonruter introduced Trac ticket #64066, proposing that WordPress default to moderate eagerness for Speculative Loading, when caching is detected. He noted the idea could provide a performance boost in WordPress 7.0 by improving preload efficiency on cached sites, but also acknowledged the need to weigh sustainability concerns around increased server load.
    • @mukesh27 asked whether a second opinion was needed, and whether any Google team members had provided feedback.
    • @westonruter replied that he had received positive input from Google, though their priorities don’t always align with those of hosts and site owners. He noted that moderate eagerness can increase bandwidth usage due to unnecessary preloads and may lead to added hosting costs.
    • @gilbertococchi shared his thoughts, emphasizing that moderate eagerness could be significantly more impactful than conservative loading, especially with Chrome’s recent introduction of a Viewport Heuristic, but stressed the importance of safeguards like persistent object caching to mitigate server load.
    • @mukesh27 summarized that @gilbertococchi was supportive of the proposal and encouraged moving the ticket into the 6.9 milestone for visibility.
    • @westonruter clarified that while he wasn’t necessarily aiming for inclusion in 6.9, he agreed to milestone the ticket for tracking purposes, with the understanding that it may still be punted.

Our next chat will be held on Tuesday, October 21, 2025 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #hosting, #performance, #performance-chat, #summary

Abha Thakor 3:33 pm on October 7, 2025
Tags: , summary   

Dev Blog editorial meeting summary, October 2, 2025

Summary of the WordPress Developer Blogblog (versus network, site) meeting, which took place in the  #core-dev-blog channel on the Make WordPress 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/.. Start of the meeting on Slack

Summary from last meeting on September 4, 2025 – props to @webcommsat

Site updates and new posts

New posts

@webcommsat: the What’s New for Developers series is a very useful tool and how we are using tags, making it easier to find the information.

Movements on some articles in progress

shout-out to @davidperez who is about to publish his first blog post next week, @magdalenapaciorek who will push her long-simmering article over the finish line 

There are two approved articles that still need a writer:

If you know someone who might be a good fit, let @bph know, and we can onboard them quickly. @bph has been doing outreach to previous writers and those who have open issues.

New topic ideas

The next three are for a new topic categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. on the Developer Blog—Artificial Intelligence and WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. This will feature some areas from the new AI core team.

@webcommsat highlighted as a potential to add to the list of useful posts for meetups.

@psykro – personal plan is to get the Abilities post published close to the 6.9 release, the MCP adapter post soon after, and then follow up with the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher AI SDK post. The aim is to try to build something that ties all three together so they can be read as a three-part series or individually. The proposal by @juanmaguitar for templates was suggested to be used as an example.

The new content items approved and @bph will create the issues later next week and assign them to writers.

It was agreed that WordPress 6.9 had some great feature in store for developers

Next meeting

The next Developer Blog editorial group meeting will be on November 2, 2025, at 15:00 UTC in the #core-dev-blog channel.

Props to @bph for reviewing the notes.

#dev-blog, #summary

Aditya Dhade 6:38 pm on September 23, 2025
Tags: , , , , summary   

Performance Chat Summary: 23 September 2025

The full chat log is available beginning here on Slack.

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

  • @westonruter shared that PR #8412 has tests added and is ready for review, though he still needs to update the description and remove the draft status.
  • @westonruter enquired about PR #9867, which enables printing script modules in the footer.
    • @b1ink0 added that work is currently underway to implement sorting behavior for script modules and their dependencies.
  • @westonruter enquired about coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. milestone #63012 regarding theme CSSCSS Cascading Style Sheets. minification.
    • @b1ink0 mentioned having a POC (minification only for 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. themes) to partially address #63012 and is working with @shyamgadde on a POC addressing the remaining points, with plans to raise PRs in the coming week.
  • @westonruter mentioned PR #9770 to iterate on fetchpriority for script modules, to allow enqueued script modules to influence the priority of dependencies (or vice versa, which is not yet totally clear).

Performance Lab 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 (and other performance plugins)

Open Floor

  • @westonruter shared that there may be a blockerblocker A bug which is so severe that it blocks a release. preventing ticketticket Created for both bug reports and feature development on the bug tracker. #63636 from being a good candidate for WordPress 6.9. The issue relates to 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. in Chrome where sending the Clear-Site-Data headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. such as during logout can slow down page performance. While this approach is preferable to using pageshow to invalidate the bfcache, the Chrome bug may require postponing the feature to 7.0.
  • @khoipro suggested adding a 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. to exclude certain taxonomies from slow term-count queries in large projects.
    • @johnbillion noted that while the suggestion didn’t seem directly related, two recent fixes in WordPress 6.9 have already reduced unnecessary term recounting #42522 and #63562.

Our next chat will be held on Tuesday, October 7, 2025 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #hosting, #performance, #performance-chat, #summary

Benjamin Zekavica 9:23 pm on September 10, 2025
Tags: , , , , , summary   

Summary, Dev Chat, September 10, 2025

Start of the meeting 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/., facilitated by @audrasjb. 🔗 Agenda post.

Announcements 📢

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

Gutenberg 21.6 is now available. The release post provides a full overview of the changes and enhancements. Thanks to @cbravobernal for preparing the notes.

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.

WordPress 6.9 Dev-Notes

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.

Discussion 💬

Allow wp-config.php without wp-settings.php

Ticketticket Created for both bug reports and feature development on the bug tracker. #5276 was discussed regarding loading wp-config.php without automatically including wp-settings.php. Opt-in approaches were considered, but concerns about back-compatibility and existing site configurations mean the ticket remains closed and is not targeted for 6.9.

Redirect on 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

Ticket #63678 proposes redirecting users to install.php when database connections are blocked due to MySQL rate-limiting. Participants agreed the 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 consistent with current error handling, with a suggestion to reuse MySQL’s native error message. It is moving forward for 6.9 consideration.

Standardizing UTF-8 handling

Ticket #63863 introduces a compat-utf8.php file to polyfill missing UTF-8 functions before compat.php is loaded. This aims to provide more consistent string handling across environments. Ongoing feedback is encouraged directly on the ticket.

Docs Team in release squads

A recent post from the Docs Team led to discussion about its role in release squads. Concerns were raised about the removal of the Docs Lead position and possible effects on onboarding and coordination. The importance of documentation was acknowledged, while there were differing views on the need for a formal lead role. It was agreed that there will not be a dedicated Docs Lead role in 6.9 for now. Instead, the focus will be on improving release instructions and checklists to ensure smoother processes.

Props to @audrasjb for review.

#6-9, #core, #dev-chat, #docs, #gutenberg, #summary

Aditya Dhade 7:02 pm on September 9, 2025
Tags: , , , , summary   

Performance Chat Summary: 9 September 2025

The full chat log is available beginning here on Slack.

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

Performance Lab 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 (and other performance plugins)

  • @westonruter flagged that the Optimization Detective plugin is overdue for a release but likely won’t ship before 6.9-beta1 due to focus on Core enhancements.
    • @westonruter reminded that getting the 1.0.0 stable release out is blocking next milestone, which includes the work @b1ink0 is doing on URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org Metrics priming.

Open Floor

  • @mukesh27 inquired about the date of the next 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 and @westonruter confirmed it is scheduled for next Tuesday (16 September 2025).

Our next chat will be held on Tuesday, September 23, 2025 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #hosting, #performance, #performance-chat, #summary

Abha Thakor 4:10 pm on September 8, 2025
Tags: , summary   

Dev Blog editorial meeting summary, September 4, 2025

Summary of the WordPress Developer Blogblog (versus network, site) meeting which took place in the  #core-dev-blog channel on the Make WordPress 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/.. Start of the meeting on Slack

Site updates and new posts

Project Board

The Dev Blog is always keen to welcome new contributors.

New published posts

Great month for the Developer Blog, and a big thanks to all the writers, reviewers and all involved.

Features on the Developer Blog by @webcommsat on OpenChannels.fm:

The WordPress Way show highlights the Developer Blog in most shows, and in September had a show completely dedicated to it and helping developers in how to use it, and encouraging contributors and new writers

Project board status

Potential new articles/ posts in progress

Highlighted GitHub discussion on the importance of a useful changelog #393

How to register border radius presets in WordPress 6.9 #394

Snippet: Allowed blocks in editor without impacting site editor #390

Setup a single source of dependencies and build tools for multiple plugins and themes #392

  • Suggestion to use this as a case study, rather than a prescriptive post on how to set-up.
  • Discussion on promoting individualized set-ups / case studies from different developers to illustrate how they use functionality. It does not have to be the “perfect” setup, but it’s the thing that works for you, which can be helpful for others.

Expecting more articles in October as WordPress 6.9 features become clear.

Reminder: if you are setting up a link to a google document in 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/ – choose the option to share it for ‘comments’ for anyone who has the link, not ‘edit’ nor ‘view only’.

@bph to move the approved discussions to issue and assign them to writers and add them to the project board. 

@areziaal – plan for a table at WCEH to promote the Dev Blog at its 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/., and thanks to help from @welcher.

Posts that need a writer

https://github.com/orgs/WordPress/projects/44/views/1

https://github.com/WordPress/developer-blog-content/issues/259

https://github.com/WordPress/developer-blog-content/issues/217

https://github.com/WordPress/developer-blog-content/issues/269

Thanks for facilitating, @marybaum

Next meeting

The next Developer Bog editorial group meeting will be on October 2, 2025, at 15:00 UTC in the #core-dev-blog channel.

Props to @bph for reviewing the notes.

#dev-blog, #summary

Benjamin Zekavica 7:58 pm on September 3, 2025
Tags: , , , , summary   

Summary, Dev Chat, September 3, 2025

Start of the meeting 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/., facilitated by @francina. 🔗 Agenda post.

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.

Forthcoming releases 🚀

WordPress 6.9

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

Discussion 💬

Revamp of Networknetwork (versus site, blog)/Sites screen with DataViews

@realloc introduced ticketticket Created for both bug reports and feature development on the bug tracker. #63885, which proposes modernizing the Network/Sites screen using DataViews and DataForm. For this to work, the 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/. endpoint for sites is also needed. Initial proof-of-concepts are available, with the goal of advancing 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 UIUI User interface together. Feedback on both design and implementation is highly encouraged.

Step-by-step integration of PHPStan into CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. workflow

There was broad agreement on integrating PHPStan into the Core workflow. Key points are ensuring compatibility with WPCSWordPress Community Support A public benefit corporation and a subsidiary of the WordPress Foundation, established in 2016., avoiding false positives related to globals or legacy code, and introducing it gradually. The plan is for incremental rule expansion, accompanied by contributor discussions.

Concerns over missing Docs Team Lead in releases

@estelaris raised concerns about the lack of a Docs Team Lead role. During the 6.8 release, 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. and HelpHub pages were coordinated too late. The discussion highlighted that Dev Notes should primarily be written by the developers implementing the changes, with the Docs team providing fallback support. Proposals included broader HelpHub access for committers and improved release checklists to ensure better planning.

Props to @francina for review.

#6-9, #core, #dev-chat, #gutenberg, #summary

Benjamin Zekavica 3:54 pm on August 27, 2025
Tags: , , , , summary   

Summary, Dev Chat, August 27, 2025

Start of the meeting 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/., facilitated by @benjamin_zekavica. 🔗 Agenda post.

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

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 has been released

Gutenberg 21.5 is now available.
The release includes several improvements and 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. fixes, with a detailed release post to follow soon.

Forthcoming releases 🚀

WordPress 6.9

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

Discussion 💬

Proposed Database Index for Performance

@josephscott proposed adding a new database index to improve performance on sites with a large number of posts or custom post types. This could speed up queries for the All Posts adminadmin (and super admin) page (see #50161). The proposal received general agreement, and further review and volunteers are needed to help carry it through to commit.

Ticketticket Created for both bug reports and feature development on the bug tracker. #63836 – HTTP Status Codes for wp_die

@callumbw95 has been working on #63836 and noted that all PR tests have passed. Further review and testing are needed before merge, and the ticket has been added to the summary so a 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. can assist.

#6-9, #core, #dev-chat, #gutenberg, #summary

Benjamin Zekavica 9:41 am on August 21, 2025
Tags: , , , , summary   

Summary, Dev Chat, August 20, 2025

Start of the meeting 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/., facilitated by @jeffpaul. 🔗 Agenda post.

Announcements 📢

The WordPress 6.9 Release Squad is assembled!

The release squad for WordPress 6.9 has been officially assembled and is ready to begin work on the upcoming version. The team will focus on enhancing performance, security, and user experience. Further details are available in the article.

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. @jorbin wrote a guide to prepare for the day.

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.

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 an issue with the register_block_pattern() function, which currently returns true even when disallowed blocks are included. This causes the pattern to not appear in the inserter and no warning is shown. 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) has been submitted to address the problem, and a second opinion is requested to ensure the issue is properly resolved. See #63765

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 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. where WordPress incorrectly redirects to wp-admin/install.php when a user is rate-limited in MySQL. A patch (PR#9223) is open and requires review. Feedback on the desired behavior, such as using wp_die(), is requested to guide the next steps. See #63678

UTF-8 Handling Improvements

@dmsnell suggested updating the wp_check_invalid_utf8() function to improve UTF-8 validation, building on previous work with seems_utf8(). This update aims to strengthen UTF-8 handling in WordPress. The community is encouraged to provide feedback before the changes are finalized. See #63837

Data Passing in Scripts

@jonsurrell, in collaboration with @westonruter, proposed adapting the data passing mechanism from Script Modules for use with classic scripts. This change would offer better performance, eliminate reliance on a global namespace, and provide an alternative to wp_add_inline_script() and wp_localize_script(). Feedback on this approach is welcome. See #58873

Emoji Detection Inline Script – Render Blocking

@westonruter discussed a potential improvement for the emoji detection script. By switching from an inline script to a script module, render-blocking could be reduced, resulting in better performance, particularly on mobile devices. Early testing has shown over a 5% improvement in Largest Contentful Paint (LCP). See #63842

Props to @francina for review.

Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"