Dev Chat Agenda – May 28, 2025

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

  • 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 is one week away 🤯 @benjamin_zekavica facilitated the organization of the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team tables. If you plan to attend (please do!), check the Core Team at WCEU 25 | Contributor Day article.

Forthcoming releases 🚀

WordPress 6.8.2 and beyond

  • The Core Team is putting together a squad for future minor releases. And yes, more volunteers are welcome.

Next 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/ version: 20.9

Gutenberg 20.9 is scheduled for release on WednesdayMay 28, 2025. So it might be out by the time we start dev chat 💪

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.

Call for Core Bug Tickets for the WordCamp Europe 2025 | Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

@benjamin_zekavica posted about WordCamp Europe Contributor Day in Basel. Do you have ahigher-priority ticket dear to your heart? This is a great time to work on it and shepherd it to resolution. Please add them to the WCEU prep post as comments so the table leads and supporters can prepare.

Where do bugs go if they are introduced in a point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.?

@sirlouen asked: Should bugs introduced during a point release cycle be moved into the next point release or the next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.? This item is not documented. Since we are moving to a different release cadence, it could use some clarity.

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