Dev Chat Agenda – November 4, 2026

The next WordPress Developers Chat will take place on Wednesday, November 4, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting focuses on upcoming releases and CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development, with time for discussions and open floor.

If you have requests for help with a ticketticket Created for both bug reports and feature development on the bug tracker. or another discussion topic, please post details in the comments section at the end of this agenda, or bring it up in Dev Chat during open floor.

Announcements 📢

WordPress 7.2

  • WordPress 7.2 Beta 4 released Nov 3rd, 2026
  • 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. 5 scheduled for Nov 10th

General

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.

  • @awetz583 is requesting input on issue #85957 – a new icon for Gallery Grid coming in 7.2.

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.

#7-2, #agenda, #core, #dev-chat

Presence API meeting summary: October 26, 2026

The Presence 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. meeting took place on Monday, October 26, 2026 at 15:00 UTC in #feature-presence-api. It also hosts the real-time collaboration (RTC) work. This week’s focus was the last two merge criteria, user testing and a security audit.

Start of the meeting in Slack

Announcements

  • Presence API 0.18.3 is out. 0.18.0 through 0.18.3 brought a per-room session hash that tells a second browser from a second tab (#815), coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.’s copy of each API function winning once it exists (#805), and a REST settings save warning an open Settings screen (#868).
  • 0.18.4 was next (#873). @huzaifaalmesbah found that logging out in one browser released post locks still held in another (#890), and the fix was in review (#893).

Follow-ups

Merge criteria

Each item from the handbook’s feature plugin criteria is tracked on #550.

  • Everything from last time except the audit is merged: touch (#830), keyboard-only (#841), JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com off (#857), HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. validation (#852, #858), Firefox and WebKit (#838), inline CSSCSS Cascading Style Sheets. in stylesheets (#825) and linted PHPUnit tests (#817). Thanks to @iamchitti and @rejaulalomkhan.
  • User testing is #835. Muhib drafted a call for testing for Make/Test in #869, with Playground links and four tasks. @huzaifaalmesbah, @iamchitti and @joefusco left feedback, and @huzaifaalmesbah offered to help get it posted on Make/Test once that feedback is worked in.
  • The security audit is #834. noruzzaman went through all four surfaces on the issue. The criterion still asks for a review from outside the repository, so @joefusco will ask the Core security team. Anyone who has done security review for core or a large 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. is welcome to take a look, in the channel or on #834.
  • #836 measures the post query cache with the plugin’s post locks off and on. A synthetic 20,000-post site is in the issue, and a few large sites on WP Engine are being lined up to measure real traffic.

Path to core

The readiness gate on #550 still has December 3 as the earliest date, eight weeks with no breaking API change from 0.17.0, and that is the earliest an initial proposal would go to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.. It also asks for three outside projects on the API, and GSE is the only one so far. Anyone building on the API, or considering it for a plugin or host, is welcome to get in touch.

Open floor

  • @jaredrethman asked on the guide whether WordPress could fire an action for each stored edit-log row, so a hosted relay could stream changes without running a process on the server (comment). The Presence API already does this for presence, firing set_presence and removed_presence on every write.
  • @alecgeatches said the engine could likely support it, with the caveat that a server-side request per row would leave the server working hard to keep up, so the cost belongs with whoever hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. in, queued or batched on their side.
  • @jaredrethman noted that gutenberg_sync_engines_room_changed already fires per write and the Redis notifier sends one publish per request, so a relay only needs that wake hint, never the rows. Editor presence already rides that hint, and carrying set_presence and removed_presence too would take Heartbeat polling off the adminadmin (and super admin). He opened #901 for what a relay would need.

Since the meeting

  • Presence API 0.18.4 shipped October 26 with the logout fix (#893), and the personal data export now leaves out reserved rows (#896).
  • 0.19.0 shipped October 29 with a presence-api.keepalive 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. (#904) and a presence-api.roomChanged action (#903), so a push transport can hold a tab’s rows and refresh presence at once.
  • 0.20.0 shipped November 1 with wp_presence_admin_state() (#924), which completes #901, and wp_presence_room_changed now fires when an edited post’s title or status changes (#915).
  • The docs are live, a first pass at automated docs for what’s built so far, generated and checked against the code.

Next meeting

Monday, November 9, 2026 at 15:00 UTC in #feature-presence-api.

#collaboration, #presence-api, #summary

Dev Chat Agenda – October 28, 2026

Dev Chat on October 28th is canceled, and will resume next week

The next WordPress Developers Chat will take place on Wednesday, October 28, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting focuses on upcoming releases and CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development, with time for discussions and open floor.

If you have requests for help with a ticketticket Created for both bug reports and feature development on the bug tracker. or another discussion topic, please post details in the comments section at the end of this agenda, or bring it up in Dev Chat during open floor.

Announcements 📢

WordPress 7.2

General

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.

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 @kirasong for the pre-publish review.

#7-2, #agenda, #core, #dev-chat

Dev Chat Agenda – October 21, 2026

The next WordPress Developers Chat will take place on Wednesday, October 21, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting focuses on upcoming releases and CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development, with time for discussions and open floor.

If you have requests for help with a ticketticket Created for both bug reports and feature development on the bug tracker. or another discussion topic, please post details in the comments section at the end of this agenda, or bring it up in Dev Chat during open floor.

Announcements 📢

WordPress 7.2

General

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.

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 @kirasong for review.

#7-2, #agenda, #core, #dev-chat

Performance Chat Summary: 20 October 2026

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, as of r64585, eliminating script/style concatenation has landed in WordPress and is included in the 7.2-beta1 release. This retires the use of load-scripts.php and load-styles.php and closed more than 10 Trac tickets, several of which were over 10 years old.
    • Script/style concatenation was only used in the login/adminadmin (and super admin) for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.’s own assets. It served its purpose, especially for HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands./1.1, but WordPress 7.2 will use a more modern and performant approach where blocking scripts and styles known to be used on the next screen are prefetched. This approach landed recently in r64120.

Our next chat will be held on Tuesday, November 3, 2026 at 16:00 UTC in the #core-performance channel in Slack.

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

Dev Chat Agenda – October 14, 2026

The next WordPress Developers Chat will take place on Wednesday, October 14, 2026, 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 7.2

General

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.

#7-2, #agenda, #core, #dev-chat

Presence API meeting summary: October 12, 2026

The Presence 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. meeting took place on Monday, October 12, 2026 at 15:00 UTC in #feature-presence-api. It also hosts the real-time collaboration (RTC) work. This week’s focus was the feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins merge criteria, and which gaps are left before a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. proposal.

Start of the meeting in Slack

Announcements

  • Presence API: What’s new went up on Make/Core on October 2.
  • Presence API 0.17.0 shipped October 8. A site can now switch off each piece it doesn’t want, and the presence functions take an $args array (#789).
  • The debugger and DB viewer moved into their own presence-debugger 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. (#760), and Presence Scenes gained arrivals, coming-back and fading-out scenes (#775).

Follow-ups

  • 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/ Sync Engines (GSE) is drafting a Make post to be published this week.
  • The collaborator-liveness work left over from #647 now lives in GSE: a second tab is GSE#147, and another device is GSE#148. #815 gives GSE#148 a way to tell a second browser from a second tab.

Merge criteria

Each item from the handbook’s feature plugin criteria is tracked on #550.

  • @huzaifaalmesbah linted the CSSCSS Cascading Style Sheets. (#811), and @rejaulalomkhan linted the PHPUnit tests (#817).
  • @iamchitti is taking Firefox and WebKit end-to-end runs, scoped to the tab coordination specs (#808).
  • Inline CSS in the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher files moves into stylesheets (#807).
  • @iamchitti took touch devices (#821), keyboard-only checks (#822) and the feature with JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com off (#823).
  • Nobody has claimed HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. validation or a security audit yet, and neither has an issue. Comment on #550 to take one.

Path to core

Post locks are the first consumer, and GSE is the first outside project on the API. The readiness gate on #550 asks for three outside projects and eight weeks without a breaking API change, counted from 0.17.0, so December 3 at the earliest. Anyone building on the API, or considering it for a plugin or host, is welcome to get in touch.

Open floor

  • Private security reporting is now enabled on the repository, thanks to @huzaifaalmesbah.
  • @iamchitti asked where the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. proposal draft is, and offered to review it this week.

Since the meeting

Presence API 0.18.0 shipped with the session hash (#815) and core’s copy of each API function winning once it exists (#805).

Next meeting

Monday, October 26, 2026 at 15:00 UTC in #feature-presence-api.

#collaboration, #presence-api, #summary

Dev Chat Agenda – October 7, 2026

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

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.

#7-1, #7-2, #agenda, #core, #dev-chat

Performance Chat Summary: 6 October 2026

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 prefetching has finally been committed in changeset 64120. The next step is to default script and style concatenation to off outside development environments in PR #13090. After that, the plan is to remove load-scripts.php and load-styles.php, along with the concatenation and compression logic that has been problematic for many years.

Open Floor

  • @westonruter noted performance gains in PHPStan 2.3.0: a full uncached analysis of WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. went from 60 seconds to 8 seconds. He shared the PHPStan 2.3.0 release post.

Our next chat will be held on Tuesday, October 20, 2026 at 16:00 UTC in the #core-performance channel in Slack.

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

Dev Chat Agenda – September 30, 2026

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

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.

  • @ericmann asked to open a conversation about the Secrets 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., TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. #66187 . A PR for integrating 2FA has been opened and broader conversation on the API approach would be valuable to establish a trajectory prior to the 7.2 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. period.

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.

#7-1, #7-2, #agenda, #core, #dev-chat