Dev Chat summary: April 15, 2026

Start of the meeting in Slack, facilitated by @amykamala Agenda post.

Announcements

WordPress 7.0 Updates

• The Path Forward for WordPress 7.0. The 7.0 release is still on pause for the time being. A new schedule is being worked out and will be announced by the 22nd. There will be another Release Candidate in name, but in practice the next release will be treated as a beta, specifically to test architectural improvements to Real Time Collaboration. Thank you in advance to everyone who helps test!

General

• Gutenberg 22.9 was released on April 8th

• Please take a look at this Twenty Twenty-Seven: Team Announcement highlighting an emphasis on mentorship and creating an entry point for new contributors.

Discussion

@annezazu has published Defining expectations for Iteration issues announcing some adjustments to iteration issue handling in the Gutenberg repo.

From @amykamala: “Finding the most current PRs and discussions can be a bit of a wild goose chase because while PRs mention tickets in their content, the fields/relationships on the right that would link PRs to a ticket, project, status, etc are not actively being used. For 7.0 theres a kan ban board but nothing in it because tickets and PRs are not being tagged. So the only way to find this info is to scroll endlessly on tickets and click on all the links in the notifications. Some of you may remember a while back I asked devs in here to please start tagging their PRs in the fields on the right.”

• @jeffpaul noted that the #core-program channel may be a good place to iterate on this topic.

Matt is requesting community reps and organizers increase emphasis on Elevating Individuals in the contributor space to to celebrate volunteers and folks who contribute in their own spare time.

From @miroku: “I can only report problems; can that be considered a contribution? I’m always struggling to figure out how to volunteer effectively”. @jorbin answered that testing and finding bugs is absolutely a contribution!

@westonruter wanted to draw attention to this issue with @wordpress/core-abilities which makes it difficult to use outside of a React context. A PR is available to fix the issue.

#7-0, #core, #core-editor, #dev-chat