The next WordPress Developers Chat will take place on Wednesday May 21, 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 ticket 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 📢
- There are no major announcements from the past week.
Forthcoming releases 🚀
WordPress 6.8.2 and beyond
- The Core 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.
Next Gutenberg 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 Wednesday, May 28, 2025.
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.
Refreshing Workflow Documentation
@sirlouen suggests updating the workflow keyword documentation, as some terms are outdated, misused, or conflicting. He proposes drafting a clearer version to publish on the blog (versus network, site) for better contributor guidance.
Improving the Local Development Environment
The current WordPress development setup makes certain testing tasks (like email testing) harder than necessary. @sirlouen recommends adding helpful tools to make the environment more complete and testing more efficient.
Reducing Redundant Test Reports
@krupajnanda points out that some simple tickets, especially UI User interface/UX User experience and accessibility 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) ones, receive too many test reports, while more complex tickets are often ignored. She proposes setting a soft limit (e.g. 5 reports) and adding a message to guide contributors to other important tickets.
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