Yearly Archives: 2025

Aditya Dhade 6:14 pm on May 20, 2025
Tags: , , , ,   

Performance Chat Summary: 20 May 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 work on #61734 / PR #8815 adding fetchpriority support for Scripts and Script Modules.
  • @spacedmonkey shared a desire to see some eyes on #59592
    • @spacedmonkey says it seems to have a massive effect for those using object caching. The change has unit tests and has been been reviewed by a non 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.. Just needs another committers to give it the thumbs up.
    • @spacedmonkey would like to land this ASAP, to allow as much time as possible to test this change.
    • @rmccue confirmed support for the proposal but cannot review the code in the short term.
    • @westonruter asked whether there’s TTFB benchmarking data available for 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..
      • @spacedmonkey noted there would’t be any noticeable difference there. This change would help high traffic site and helps database and object cache performance.
      • @tillkruess noted It will just reduce memory usage in the cache significantly, or make it easier to keep it low.
  • @spacedmonkey noted that #58001, #63021, and #57496 are still awaiting a second round of review.

Open Floor

  • @b1ink0 brought up some confusion around the 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 timing, asking if the schedule should be revisited to avoid conflicts. (Bug scrub schedule link)
    • @westonruter asked if the time had already been moved to avoid conflicting with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat.
    • @westonruter confirmed that, according to the Make Meetings page, it had not been adjusted.
    • @swissspidy suggested moving the bug scrub to Tuesdays on alternate weeks from office hours.
    • @westonruter and @flixos90 both supported the idea.
    • @swissspidy updated the Make Meetings page and Bug scrub schedule, then shared the schedule for the next meetings as follows:
      • May 27 – bug scrub (potentially led by @adamsilverstein)
      • June 3 – office hours (@swissspidy would probably cancel that one because of 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. Europe)
      • June 10 – bug scrub
      • June 17 – office hours

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

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

Krupa Nanda 8:16 am on May 15, 2025
Tags: ,   

X-post: Building the Testing Use-Case

X-comment from +make.wordpress.org/test: Comment on Building the Testing Use-Case

Benjamin Zekavica 8:13 pm on May 14, 2025
Tags: , , ,   

Summary, Dev Chat, May 14, 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 📢

A Month in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. – April 2025

In case you haven’t seen it yet, here’s a statistical report from the month of April published by the Core Team. You can find more details in the article.

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/ 20.8 is now available

The new version of the Gutenberg pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. is now available in our plugin directory.

AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Focused Bug Scrub

@jorbin is hosting an Accessibility-Focused Bug Scrub tomorrow at 15:30 UTC in #core to help move tickets forward. More detailed information you can find here.

Forthcoming releases 🚀

WordPress 6.8.2 and beyond

The Core Team need to set up a release squad, a plan/scope and a schedule for 6.8.2 (and beyond)

Discussion 💬

Call for Topics for the Dev Chat agenda

@sirlouen suggested to publish the “Call for Topics for the Dev Chat agenda” earlier to give contributors more time to suggest topics. @benjamin_zekavica, speaking for the Team Reps, noted that while it can be challenging due to time constraints, they will aim to publish the Call for agenda 1–2 days in advance and update it as needed.

He supports the idea of raising topics early and will discuss improvements with the other reps. Further updates on this will follow.

PHPCSPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. for Class FTPFTP FTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. https://codex.wordpress.org/FTP_Clients files

In the discussion on ticketticket Created for both bug reports and feature development on the bug tracker. #63436, it was agreed that PHPCS should not be applied to the FTP class files. These files come from an old external library, and applying coding standards would only make sense if WordPress fully adopts the code. There was also agreement on the need for clearer rules and improved documentation.

#6-8, #dev-chat, #summary

Aaron Jorbin 1:04 pm on May 14, 2025
Tags: , ,   

Accessibility Focused Bug Scrub – 15 May 2025

In celebration of Global Accessibility Awareness Day, a scrub of stagnant Accessibility focused tickets will be held in the #core slack channel at Thursday, May 15, 2025 at 15:30 UTC. The goal of this scrub is to help move tickets towards a resolution (which may include being added to a future milestone or closing).

If you’ve never participated in 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. scrub, reading the documentation on leading a bug scrub will help you understand what to expect!

Thanks to @joedolson for pre-publication review

#accessibility, #bug-scrub, #core-accessibility
Francesca Marano 9:42 pm on May 13, 2025  

Dev Chat Agenda – May 14, 2025

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

  • In case you missed it, A Month in Core – April 2025 is out.
  • ETA: Gutenberg 20.8 is out! Tentative: 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/ 20.8 might be released in time for the dev chat. An update will be given.

Forthcoming releases 🚀

WordPress 6.8.2 and beyond

  • The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases.

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.

Benjamin Zekavica 8:26 pm on May 7, 2025
Tags: , , ,   

Summary, Dev Chat, May 7, 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 📢

WordPress 6.8.2 and beyond

The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team need to set up a release squad, a plan/scope and a schedule for 6.8.2 (and beyond)

Forthcoming releases 🚀

Call for 6.8.x release leads

@michelleames and @jeffpaul published a Call for 6.8.x Release Managers. Anyone interested to lead a 6.8.x release can drop a comment in this P2P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. post.

Discussion 💬

CSSCSS Cascading Style Sheets. Regressions in 6.8

@luminuu reported regressions in several third-party plugins caused by bugfixes introduced in WordPress 6.8 (PR #64770). Affected projects include Jetpack and WooCommerce. One key issue—buttons stretching full width—was tracked in Trac ticket #63373 and is scheduled to be fixed in version 6.8.2.

The group discussed how to prevent similar issues in the future. Suggestions included:

  • Introducing a 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. format to track frontend CSS changes per release
  • Improving visibility of such changes before they ship
  • Investing in visual regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. testing
  • Collecting and surfacing CSS-related changes in “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/?” posts

Better communication, testing, and transparency are needed to reduce the risk of regressions in future releases.

Thanks to @audrasjb for proofreading this post.

#6-8, #core, #dev-chat, #summary

Aditya Dhade 6:06 pm on May 6, 2025
Tags: , , , ,   

Performance Chat Summary: 6 May 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 asked if any performance-related fixes were included in the WordPress 6.8.1 release.
    • @b1ink0 confirmed that the update focused primarily on general 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 across WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and the 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, with no specific performance items.
  • @westonruter noted that he has some pending PRs to review and merge.

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)

  • @flixos90 has started work on the new View Transitions feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins (see issue #1997). The work is being tracked through a series of iterative PRs, starting with theme support and dynamic transition name handling. It builds on the experimental Core PR wordpress-develop#8370 and will include a UIUI User interface for customizing transitions.
    • @flixos90 plans to work on the next PRs later this week, with most work focused on porting the experimental code into plugin shape.
    • When asked if the plugin would be considered stable or experimental upon release by @mukesh27, @flixos90 noted that it depends on the final feature set and the team’s evaluation at that time.
  • @mukesh27 briefly noted progress on Accurate Sizes (part of the Auto Sizes plugin) and will share a more detailed update later this week.

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

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

Jb Audras 8:06 am on May 6, 2025  

Dev Chat Agenda – May 7, 2025

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

Additional items will be referred to in the various curated agenda sections below. 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.

Announcements 📢

Forthcoming releases 🚀

WordPress 6.8.2 and beyond

  • The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team need to set up a release squad, a plan/scope and a schedule for 6.8.2 (and beyond)

Highlighted posts ✨

Discussions 💬

The discussion section of the agenda is to provide a place to discuss 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.

Jb Audras 5:47 pm on May 4, 2025
Tags: ,   

X-post: A Month in Core – April 2025

X-comment from +make.wordpress.org/updates: Comment on A Month in Core – April 2025

Jb Audras 9:41 pm on April 30, 2025
Tags: , , ,   

Summary, Dev Chat, Apr 30, 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 📢

WordPress 6.8.1 is now available 🥳

WordPress 6.8.1 was released right after the dev chat. It is a maintenance release.

For now, 6.8 is identified as the last major release of the year.

Forthcoming releases 🚀

WordPress 6.8.2

There are currently 7 tickets in the 6.8.2 milestone on Trac. Bugfixes currently located in milestone 6.9 can probably start to be moved to 6.8.x milestones, but 6.8.2 will most probably still be focused on remaining issues/regressions found on 6.8.

Call for 6.8.x release leads

@michelleames and @jeffpaul published a Call for 6.8.x Release Managers. Anyone interested to lead a 6.8.x release can drop a comment in this P2P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. post.

Discussion 💬

@sirlouen wanted to bring attention to this ticketticket Created for both bug reports and feature development on the bug tracker.: #43936. He commented this ticket with a recap of everything that must be known if someone doesn’t want to read all the way through. @audrasjb pointed out that this ticket is a good candidate for a further 6.8.x release, as 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. shouldn’t add any new file.

@sirlouen pointed out that publishing a call for dev chats topics should ideally be posted on the Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Slack channel, ideally 2 days before each meeting to help gather topics for the agenda. @audrasjb proposed to post such a call on next Monday and to iterate on this process.

@sirlouen added another topic coming from the Core Test Team: “I’m writing a guide on creating Testing Use-Cases for core developers. The thing is that I’ve found over the period of ~100 ticket reviews, that most old stuck tickets with patches that have been pretty much abandoned, the main cause is that the patch creator did not provide enough information to test and help patch progress (even sometimes other reviewers asked for it). I’ve been ideating some examples and ideas, to help people build testing cases, and I’m going to publish this in the Test WP blogblog (versus network, site).” He is looking for people able and willing to review his proposal. @audrasjb volunteered.

@justlevine proposed to discuss the following ticket: #62622: Bump minimum PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher version to 7.4.
This ticket is on @johnbillion‘s radar. Everyone agreed that this ticket is a major goal for 6.9.

#6-8, #core, #dev-chat, #summary