The April 15, 2026 WordPress Core developer chat highlighted ongoing developments around the delayed WordPress 7.0 release, recent Gutenberg updates, and efforts to improve contributor experience. The release schedule for 7.0 remains paused as the team works on architectural improvements, including Real Time Collaboration features. Meanwhile, the community is refining workflows for issue management and emphasizing mentorship to support new contributors.
Key Takeaways
- WordPress 7.0 release remains on hold; new schedule expected by April 22 with a beta focusing on Real Time Collaboration testing.
- Gutenberg 22.9 was released April 8, continuing block editor enhancements.
- Contributor processes are being refined, including better tagging of pull requests and iteration issue handling.
- A renewed focus on mentorship and recognizing volunteer contributions is underway to grow and support the community.
- Technical fixes are in progress, such as improving the usability of
@wordpress/core-abilitiesoutside React contexts.
WordPress 7.0 Release: Still on Pause with New Testing Approach
The WordPress 7.0 release cycle remains paused as the core team rethinks the path forward. Originally anticipated for an imminent launch, the release is now entering a new phase focused on architectural enhancements, particularly Real Time Collaboration capabilities. Rather than a typical Release Candidate, the upcoming build will serve as a beta to test these complex features in real environments.
In practice, this means that while the version number will advance, the release emphasis shifts from feature completion to stability and collaboration testing. This approach acknowledges the complexity of integrating Real Time Collaboration into WordPress’s architecture, which requires extensive community testing to identify edge cases and ensure reliability.
The development team plans to announce an updated release schedule by April 22, providing clarity to agencies, plugin developers, and site operators who depend on timely updates. This pause and reorientation reflect a mature release management process that prioritizes quality and long-term maintainability over rushing deadlines.
Gutenberg 22.9 Release and Iteration Issue Process Updates
On April 8, the Gutenberg plugin team released version 22.9, continuing their steady cadence of block editor improvements. This release includes various bug fixes and enhancements, supporting the broader WordPress editing experience.
Alongside the technical updates, the team introduced process changes for managing iteration issues in the Gutenberg repository. Contributor Ann O’Malley (@annezazu) published guidelines to clarify expectations around iteration issue handling, aiming to streamline development workflows.
One persistent challenge is tracking pull requests (PRs) and their relationships to tickets. As noted by contributor Amy Kamala (@amykamala), the current system lacks consistent tagging, making it difficult to locate relevant PRs and discussions. The absence of active use of metadata fields on the right side of GitHub issues means contributors often resort to scrolling through numerous notifications, which is inefficient and error-prone.
To address this, the team is encouraging developers to tag PRs properly to link them to tickets, projects, and statuses. This change will improve transparency and coordination across contributors, especially important given the complexity of the 7.0 release cycle.
Fostering Contributor Growth Through Mentorship and Recognition
The Twenty Twenty-Seven theme team announced a renewed emphasis on mentorship and creating accessible entry points for new contributors. This initiative reflects an ecosystem-wide awareness that sustainable growth depends on welcoming and supporting volunteers at all skill levels.
Community lead Matt has called on representatives and organizers to elevate individuals within the contributor space, recognizing efforts beyond code contributions. This includes celebrating those who report bugs, test features, or improve documentation.
For example, contributor Miroku expressed uncertainty about how to contribute effectively, questioning if reporting problems counts as volunteering. The response from core team member Jorbin confirmed that testing and bug reporting are valuable contributions, reinforcing an inclusive definition of participation.
Such recognition helps reduce barriers to entry and encourages broader community engagement, which is critical for WordPress’s open-source health.
Technical Fixes and Developer Experience Improvements
On the technical front, contributor Weston Ruter highlighted an issue with the @wordpress/core-abilities package, which currently has limited usability outside React contexts. This limitation affects developers seeking to implement permission management in non-React environments.
A pull request is underway to resolve this, reflecting ongoing efforts to improve developer experience across the WordPress ecosystem. These incremental fixes are essential as the codebase grows in complexity and diversifies its user base.
What This Means for WordPress Users
For WordPress developers and agencies, the ongoing delay and re-scoping of WordPress 7.0 mean planning for a longer testing and integration window. The focus on Real Time Collaboration indicates WordPress’s commitment to modernizing the editing experience, but it also introduces new complexities. Teams should monitor the upcoming beta releases closely and incorporate testing into their workflows to avoid surprises at launch.
Site operators can expect continued improvements in Gutenberg through incremental plugin releases like 22.9, which refine the block editor’s stability and features. However, they should be prepared for a slower major release cadence as architectural changes take precedence.
The heightened focus on contributor mentorship and recognition signals a healthier community environment. For agencies and freelancers, this could mean more opportunities to engage with WordPress development, whether through bug reporting, testing, or mentoring newcomers. Participating actively can provide early insights into upcoming features and help shape the platform’s direction.
Finally, the technical fixes in developer packages like @wordpress/core-abilities will improve flexibility for plugin and theme developers building outside of React, broadening the ecosystem’s inclusivity.
Frequently Asked Questions
Why is the WordPress 7.0 release currently on pause?
The release is paused to focus on architectural improvements, especially Real Time Collaboration features, which require extensive testing to ensure stability before finalizing the release.
What changes are being made to the Gutenberg development process?
The team is refining how iteration issues and pull requests are managed, encouraging better tagging and clearer expectations to improve collaboration and tracking of development progress.
How can new contributors get involved and be recognized?
New contributors can participate by testing, reporting bugs, or improving documentation. The community is emphasizing mentorship and celebration of all volunteer efforts, not just code contributions.
What is the significance of the fix to @wordpress/core-abilities?
The fix will make this package easier to use outside of React contexts, allowing more flexibility for developers building plugins and themes with different technology stacks.
