Dev Chat Agenda – April 23, 2025

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

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

Worth saying once more! WordPress 6.8 “Cecil” is now available! 🐣

WordPress 6.8 was released as scheduled and it was named after the legendary jazz pianist Cecil Taylor.

Forthcoming releases 🚀

WordPress 6.8.1

@michelleames posted a Call for 6.8.x Release Managers. Getting involved with minor releases is a great way to start being more active in the release process. Highly recommended!

A calendar with bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs will be posted soon.

Highlighted posts ✨

Read about the WordPress 6.8 performance improvements.

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

@mamaduka and @karmatosed are planning to start working on the backlog management in the 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/ repository. The plan is to close non-actionable issues/tickets and stale PRs.
@sirlouen is bringing attention to two items that we started discussing in previous dev chat and didn’t complete:
- https://make.wordpress.org/core/2025/04/22/summary-dev-chat-april-9-2025-2/#core-trac-workflow-keywords-issue
- https://make.wordpress.org/core/2025/04/22/summary-dev-chat-april-9-2025-2/#comment-47644

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.

David Levine 12:31 pm on April 23, 2025

Probably won’t be able to attend, but I’m still lobbying to get a discussion/assistance moving forward on:

1. https://core.trac.wordpress.org/ticket/49442 (a `parse_blocks` 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., so we can stop dumping parsing functionality on `render_blocks` )

2. https://core.trac.wordpress.org/ticket/61175 (Implementing PHPStan in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.).

In parallel to #2, I’m remediating individual PHPStan smells against https://core.trac.wordpress.org/ticket/63268 (please feel free join in). It’s officially labeled as targeting 6.9, although my understanding is most of the associated patches would make great 6.8.x candidates.
- David Levine 12:40 pm on April 23, 2025
  
  (Last time I see these recorded in summaries were on https://make.wordpress.org/core/2025/01/17/summary-dev-chat-january-15-2025/ . I also brought it up last week https://wordpress.slack.com/archives/C02RQBWTW/p1744819355471259 though it doesnt seem to have made it into the summary https://make.wordpress.org/core/2025/04/22/summary-dev-chat-april-9-2025-2/ 😔 )