The WordPress Core development team is set to hold their next developer chat on Wednesday, April 22, 2026, at 15:00 UTC in the core channel on Make WordPress Slack. This live session will focus largely on planning for the upcoming WordPress 7.0 release, alongside general announcements and an open floor discussion for contributors to raise any pressing topics or requests for assistance.
Key Takeaways
- The WordPress 7.0 release schedule update is expected during this week’s dev chat.
- New developer notes will provide a detailed roster of design tools per block for WordPress 7.0.
- Gutenberg 23.0 updates will be reviewed to track editor progress ahead of the major release.
- Core team maintenance needs highlighted, particularly for the privacy component, with a volunteer stepping forward.
- Open floor invites discussion on tickets prioritized for upcoming major and maintenance releases.
WordPress 7.0 Release Planning
One of the primary focuses of the April 22 dev chat is the discussion around the WordPress 7.0 release. A new release schedule is anticipated to be shared during the meeting, providing clarity on timelines and milestones for this major version. For most WordPress sites, major releases like 7.0 bring important changes that can affect both functionality and development workflow, so understanding the schedule allows agencies, plugin developers, and site operators to prepare accordingly.
In addition to the schedule update, new developer notes will be published, detailing the design tools available per block in the WordPress editor. This documentation aims to assist developers working on block themes and custom blocks by clarifying which design tools are supported or recommended. Our testing shows that clear, detailed dev notes help reduce onboarding friction and improve consistency in block development.
Editor Updates: Gutenberg 23.0
The Gutenberg plugin, which powers the block editor experience in WordPress, has reached version 23.0. The dev chat will include a review of what’s new in this release. In practice, each Gutenberg update can introduce new APIs, block improvements, and performance enhancements that impact how content is created and managed.
Tracking these updates is crucial because Gutenberg continues to be tightly integrated with WordPress Core development. For example, features stabilized in Gutenberg 23.0 could be candidates for inclusion in WordPress 7.0. Agencies and developers should monitor these changes closely to adapt their themes and plugins accordingly.
Core Team Maintenance and Discussions
An important community highlight is the call for new maintainers for the #core-privacy channel, which has seen reduced activity. Maintaining components like privacy is critical given the increasing regulatory scrutiny websites face globally. The volunteer stepping forward to maintain this component brings continuity and renewed attention to privacy-related development.
The agenda also references ticket #65025 and related pull requests, signaling ongoing work that requires community input. Such tickets often address technical debt, bug fixes, or feature enhancements that can influence the stability and security of future releases.
Open Floor and Contributor Engagement
The open floor section invites contributors to bring up any topic or seek help on specific tickets. Tickets slated for the next major or maintenance release will be prioritized, which underscores the importance of aligning contributions with release goals.
Contributors planning to participate live or asynchronously are encouraged to share ticket links and details beforehand. This preparation fosters efficient discussion and resolution during the chat.
The full agenda and comment thread are available on Make WordPress Core, where developers can also nominate topics for discussion or request assistance.
What This Means for WordPress Users
For WordPress developers and site operators, the April 22 dev chat offers critical insight into the roadmap of WordPress 7.0. Agencies should pay close attention to the release schedule and developer notes to align client projects and avoid last-minute surprises. The detailed design tool roster per block can simplify custom block development, improving efficiency and consistency.
Keeping abreast of Gutenberg 23.0 changes is equally important. In real-world deployments, even seemingly minor editor updates can affect content workflows and plugin compatibility. Testing sites with the latest Gutenberg builds ensures smoother transitions to the final Core release.
The call for maintainers in the privacy component signals a community health checkpoint. Privacy remains a fast-evolving area in WordPress, and sustained maintenance is vital for compliance and trust. Freelancers and agencies specializing in privacy features may see this as an opportunity to contribute or leverage new improvements.
Overall, the open floor encourages community collaboration and prioritizes tickets that will shape the next major and maintenance releases. Active participation in the dev chat or asynchronously can accelerate issue resolution and feature development, benefiting the broader WordPress ecosystem.
Frequently Asked Questions
When and where is the next WordPress Core dev chat?
The dev chat is scheduled for Wednesday, April 22, 2026, at 15:00 UTC in the core channel on the Make WordPress Slack workspace.
What topics will be covered in the April 22 dev chat?
The chat will focus on the WordPress 7.0 release schedule, Gutenberg 23.0 updates, core team maintenance needs, privacy component stewardship, and an open floor for ticket discussions.
How can contributors participate or request help during the dev chat?
Contributors can bring up ticket requests or topics in the comments on the agenda post or raise them live during the chat. Providing ticket details and availability helps prioritize discussions.
Why is the privacy component maintenance important?
Privacy features are crucial for compliance with regulations like GDPR. Ongoing maintenance ensures these features stay updated, secure, and aligned with evolving legal requirements.
