Dev Chat Agenda – December 10, 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, December 10, 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 📢

WordPress 6.9 is now available!

WordPress 6.9 is now available for download. Huge thanks to all contributors who made this release possible.

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/ 22.2 has been released!

Gutenberg 22.2 has been released and is available for download!

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.

6.9.1 Planning

@jorbin notes that planning for 6.9.1 should begin. Discussion is needed to determine whether a maintenance release is required imminently based on the current tickets or if targeting a date after the first of the year is more appropriate.

Missing “Needs 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. / Needs PR” label

@sirlouen notes that the Gutenberg repo does not have a clear label to show when an issue is ready for a patch or PR. Some issues like https://github.com/WordPress/gutenberg/issues/73832 are fully triaged but still unclear if they need development or more testing. A simple label would help developers see which issues they can work on.

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.

#6-9, #agenda, #core, #dev-chat

SirLouen 6:46 pm on December 9, 2025

Thanks @benjamin_zekavica

I would like to add a discussion topic:
In the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor 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/, after a couple of months already, I’ve been playing around with the flow, and I still think there is something missing: a “Needs 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.” (or “Needs PR”) tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.). Back in the day I proposed this, but I was waiting to get much more experience before rethinking it. After some months, I think that I see this clearly now.

At this moment, 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/ repo, adds automatic tags on creation, and if there is also a manual triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., it’s still very challenging to see which tickets are pending triage and which are fully triaged (incl. a repro report) and are ready for a PR. For example: https://github.com/WordPress/gutenberg/issues/73832, has been added with full triage (all tags), but its still unclear if its a patch ready or if it `Needs reproduction/testing` (probably a repro report would be ideal here but its not tagged).

In the case of someone willing to contribute with code, being able to 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. for a tag that gives a clear indication that the ticketticket Created for both bug reports and feature development on the bug tracker. needs a developer is a clear advantage to facilitate things. Looking at how other repos do it, for example, in the `php-src` repo, they use a tag called `Status:Verified` to confirm that it needs a PR (or if already has).

I could add more information tomorrow in the meeting about this topic if there are doubts.

Also noting, that currently there is a tag called `Needs Dev`. I would encourage to take this for this purpose and if we could reach a consensus, it would be great to reference this meeting in the future.
- Benjamin Zekavica 2:39 pm on December 10, 2025
  
  @sirlouen Thank you 🙂 I added it to the agenda.