Some links on this page are affiliate links. We may earn a commission when you click through and make a purchase, at no additional cost to you.
The WordPress Core team convened on May 6, 2026, for their regular development chat to discuss progress on WordPress 7.0. The conversation highlighted the upcoming release candidate 3 (RC3), scheduled for May 8, alongside important decisions regarding the new custom table infrastructure known as RTC (Relational Table Cache). Ongoing efforts to streamline contributor onboarding and documentation also featured prominently.
Key Takeaways
- WordPress 7.0 Release Candidate 3 is set for May 8, with a call for host testing on the RTC feature.
- RTC custom table introduction decision finalized, marking a significant core schema update.
- New proposal to auto-generate Block Editor Handbook docs from block.json aims to ease contributor engagement.
- Active scrubs planned for both WordPress 7.0 milestone tickets and Gutenberg blocks to ensure release readiness.
- Systems team has been involved in RTC testing; formal process for future schema changes deemed unnecessary due to rarity.
WordPress 7.0 Release Candidate 3 and RTC Testing
The team announced that WordPress 7.0 Release Candidate 3 (also referred to as “new Beta 1”) will be released on Friday, May 8. A critical part of this release cycle is the ongoing testing of the RTC system, a custom table feature designed to optimize performance and scalability by introducing new database schema elements tailored for block editor usage.
Hosts including Bluehost, Kinsta, GoDaddy, XServer, WordPress.com, and Ionos have contributed to RTC testing efforts. Their participation is crucial for validating RTC’s behavior in real-world, high-traffic environments. The team issued a call for additional testing submissions, emphasizing the importance of thorough vetting before the final release.
After extensive discussions, the decision to introduce RTC into WordPress 7.0 was finalized, reflecting confidence in the feature’s stability and value. This change marks one of the more significant schema updates in recent WordPress history, aiming to improve data handling efficiency for complex block content.
Improving Contributor Experience and Documentation
A notable proposal surfaced to auto-generate Block Editor Handbook documentation directly from block.json files. This initiative targets reducing friction for contributors by automating documentation updates in sync with block development. It complements broader efforts to make WordPress contributions more approachable, especially for those involved in Contributor Days.
The team encouraged those who have helped with Contributor Day tables to engage with this new documentation effort, highlighting its potential to streamline onboarding and knowledge sharing. The handbook is envisioned as a living resource that evolves alongside block editor enhancements, supporting both new and experienced contributors.
Ticket Scrubs and Release Readiness
With 37 open tickets still assigned to the WordPress 7.0 milestone, the team acknowledged the need for focused scrubs to ensure no critical fixes are overlooked. @jorbin proposed a dedicated 7.0 scrub session following the chat, while @juanmaguitar scheduled a Gutenberg block scrub for the upcoming Thursday.
These scrubs target clearing backlog tickets and clarifying statuses, such as the ambiguous status of the about page ticket (#64536). These focused efforts reflect the team’s commitment to maintaining a high-quality release by tightening feedback loops and resolving outstanding issues promptly.
Systems Team Involvement and Schema Change Process
A key discussion point centered on the RTC custom table’s integration process and the need for systems team feedback. @joefusco inquired about the existence of a formal process for systems team review of new database schema proposals, noting that RTC’s code and testing infrastructure are production-ready, including a standalone testing plugin.
In response, @desrosj confirmed ongoing systems team involvement and active testing. The consensus among attendees was that formalizing a rigid process for future schema changes is likely unnecessary given the infrequency of such changes. However, the current approach involves close collaboration and testing between core contributors and the systems team to ensure stability.
What This Means for WordPress Users
The inclusion of RTC in WordPress 7.0 represents a milestone in the platform’s evolution. For developers and agencies, this means preparing for a new database schema that can enhance block editor performance but may also require updated testing and monitoring practices. We recommend that managed hosting providers and site operators prioritize RTC testing to identify any hosting environment-specific issues early.
From a contribution standpoint, the move toward auto-generating documentation from block.json files signals WordPress’s ongoing effort to lower the barrier to entry for new contributors. This should simplify how developers maintain block documentation and encourage more participation in the Gutenberg project.
Practitioners should monitor the outcome of the scheduled scrubs and the finalization of the Field Guide, which will provide detailed guidance on the 7.0 release. Staying informed and involved in testing cycles remains critical as the release candidate phases progress.
Finally, the collaborative approach to RTC’s introduction—with active testing by multiple hosting providers and the systems team—demonstrates WordPress’s commitment to stability even when introducing significant architectural changes. While a formal schema change process is not planned, the transparent communication and testing protocols established set a useful precedent for future core development.
Frequently Asked Questions
What is the RTC feature in WordPress 7.0?
RTC (Relational Table Cache) is a new custom table system designed to optimize WordPress’s database performance, especially for the block editor. It introduces schema changes to handle block data more efficiently.
Who should test the RTC feature before release?
Managed hosting providers, site operators, and developers are encouraged to test RTC in staging or production environments, ideally on high-traffic sites, to catch issues early and provide feedback before the final WordPress 7.0 release.
Will the RTC schema changes affect existing plugins or themes?
In practice, RTC aims to be backwards compatible, but plugins or themes that interact deeply with block storage or the database may need testing and possible updates to ensure compatibility with the new schema.
Is there a formal process for introducing database schema changes in WordPress core?
Currently, no formalized process exists due to the rarity of such changes. Instead, schema proposals undergo close review and testing by the core and systems teams before merge.
