Performance Chat Summary: 11 August 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

  • @b1ink0 asked whether there was anything the team would like to focus on for the WordPress 7.2 release, referencing the performance-focused Core Trac tickets.
    • @westonruter said he would love to get script/style concatenation ripped out in favor of using preloads, which would be a big improvement to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., especially from a tech debt perspective.

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 shared that he pushed out a security fix for Optimization Detective the previous week. That process brought to light a deficiency in the deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. script where it could inadvertently try to publish a release for an older version, so he opened PR #2620.

Open Floor

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

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

Dev Chat Agenda – August 11, 2026

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

Note: Dev Chat has been moved to Tuesdays at 15:00 UTC for the duration of the 7.1 release cycle.

7.1

  • 7.1 RC1 was released Wed August 5th.
  • A silent RC2 security release was released on August 6th.
  • RC3 scheduled for Wednesday, August 12th.
  • WordPress 7.1 Field Guide
  • 7.1 Release Candidate phase
  • As of Aug 10th, 7.1 is branched. Committers: Trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. is open for 7.2 and the 7.1 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". requires double sign off.

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

    Dev Chat Agenda – August 4, 2026

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

    Note: Dev Chat has been moved to Tuesdays at 15:00 UTC for the duration of the 7.1 release cycle.

    7.1

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

    Performance Chat Summary: 28 July 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 highlighted #65634, a minor improvement to the development environment to make it easier to do performance tests so it is more reflective of an actual normal environment, with a small 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. ready for review.
    • For #65215, @westonruter shared that there is some feedback on the PR #11790 that has not been actioned yet.

      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 highlighted PR #2601, which updates wp-coding-standards/wpcs to 3.4.1, and shared that there was an important security release for WPCSWordPress Community Support A public benefit corporation and a subsidiary of the WordPress Foundation, established in 2016.. While it has been applied to the Performance repo, anyone with other repositories using an older version should update as soon as possible.
      • @mukesh27 shared that work has been ongoing over the past few weeks on accurate sizes for the Gallery 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. and that the full PR will soon be ready for review.
      • @b1ink0 asked for feedback on a comment in PR #2336. @westonruter shared that it has been added to saved items.

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

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

      Dev Chat Agenda – July 28, 2026

      The next WordPress Developers Chat will take place on Tuesday, July 28, 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 📢

      Note: Dev Chat has been moved to Tuesdays at 15:00 UTC for the duration of the 7.1 release cycle.

      7.1

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

      Dev Chat Agenda – July 21, 2026

      The next WordPress Developers Chat will take place on Tuesday, July 21, 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 📢

      Note: Dev Chat has been moved to Tuesdays at 15:00 UTC for the duration of the 7.1 release cycle.

      7.0.2

      7.1

      • 7.1 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. 3 is due for release this Wednesday, July 22th. The release party starts at 15:00 UTC.
      • From @adrianduffell:
        • There’s about 140 Trac tickets milestoned for 7.1. It would be good for owners to start punting the tickets that can be safely picked up in a future release. This will help to make the remaining 7.1 priorities clearer.
        • Highlighting a few bugs with simple PRs needing review. It might be possible to merge them before beta 4 next week:

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

      Performance Chat Summary: 14 July 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 a late submission for inclusion in WordPress 7.1 and requested reviews for PR #12514, which provides a mechanism for hosting providers to change the default Speculative Loading eagerness and mode without requiring an mu-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..
        • @swissspidy shared that CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. was a bit hesitant in the past to introduce new constants, let alone environment variables, and asked whether this is something hosts could control with an mu-plugin instead.
        • @westonruter replied that there is such an environment variable and constant for wp_get_environment_type().
        • @westonruter shared that configuration of Realtime Collaboration was also being done via environment variables.
        • @westonruter shared that the reason for the environment variable is explained in the Realtime Collaboration discussion, where a host may not be able to control all the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher being used in a hosted site and hosts could potentially control the PHP being used but may not “manage” their hosted WordPress sites, so doing so would be a violation of sorts of what their customers expect.

      Performance Lab Plugin (and other performance plugins)

      • @westonruter shared that there are some new PRs that need reviewing, but has not had time to review them yet due to work on Core tickets and expressed hope that there would be more time available for reviews within the next week.

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

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

      Dev Chat Agenda – July 14, 2026

      The next WordPress Developers Chat will take place on Tuesday, July 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 📢

      Note: Dev Chat has been moved to Tuesdays at 15:00 UTC for the duration of the 7.1 release cycle.

      7.1

      • 7.1 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 is due for release this Wednesday, July 15th. The release party starts at 15:00 UTC.
      • New 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.: Consistent navigation in WordPress 7.1 with persistent toolbar

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

      Dev Chat Agenda – July 8, 2026

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

      7.1

      • 7.1 bug scrub schedule
      • 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 is scheduled for next week on Wednesday July 15th at 15:00 UTC
      • Heads up CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Committers: Tech and Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. leads have started tagging tickets for 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.. Deadline for publishing is August 3rd, and the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. targeted for the 4th (just before RC1).
      • Merge Proposal: Expanding WP Core Abilities
      • Classic block will NOT be hidden from inserter in WP 7.1

      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.

      • Dev Chat scheduling during 7.1 cycle

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

      Dev Chat Agenda – July 1, 2026

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

      7.1

      • Roadmap for 7.1
      • Recent proposals:
      • Recent 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.:

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