WordPress 7.0, a major release with significant updates including real-time collaboration features, has hit an unexpected delay. Announced earlier this week on the Make WordPress Core blog, the release will return to beta testing despite previously entering the Release Candidate phase. This decision aims to address critical feedback and ensure stability for the final release. While unprecedented, the delay reflects WordPress’s commitment to quality and user experience.
Key Takeaways
- WordPress 7.0’s final release is delayed, with additional beta-style release candidates expected.
- Real-time collaboration features are under scrutiny to address stability concerns before launch.
- Trunk commits are paused until further notice; only bug fixes introduced in this cycle are allowed.
- Testing is recommended via nightly builds using the WordPress Beta Tester plugin.
- A revised final release schedule will be published by April 22, 2026.
Why the Delay Was Necessary
The decision to delay WordPress 7.0 stems from feedback about the real-time collaboration feature, a cornerstone of this release. Contributors raised concerns about stability and edge-case issues during initial testing. While the feature promises transformative capabilities for Gutenberg users, it also introduces complex technical challenges.
Returning to beta testing after reaching Release Candidate status is unprecedented in WordPress history. This rollback reflects the project’s leadership prioritizing a thorough review over adhering to the original timeline. Such a move highlights the intricate balance between innovation and reliability in open-source development.
Updated Policies for Contributors
Commit Guidelines
During this pause, trunk commits are closed to avoid merge conflicts and ensure focus on the 7.0 branch. Backporting to the 7.0 branch will require double sign-off from committers. Contributors are encouraged to use the dev-feedback and dev-reviewed keywords in Trac to streamline this process.
Allowed Changes
Only bug fixes introduced in this release cycle, test coverage improvements, and critical feature removals are permitted. Stability-related changes to real-time collaboration and the Connectors admin screen will be prioritized.
String Freeze
To prevent additional workload for translation teams, new strings are discouraged unless critical. Exceptions will be tagged with i18n-change and communicated to Polyglots via Slack and Trac.
Revised Testing and Version Numbering
Nightly builds for WordPress 7.0 are now live and available for testing. Site owners and developers can access these builds through the WordPress Beta Tester plugin by selecting the “Bleeding edge” channel and “Nightlies” stream.
Due to technical limitations with versioning, new beta releases will retain the Release Candidate (RC) designation, starting with RC3. While unconventional, this approach ensures compatibility with version comparison functions and minimizes confusion for testers.
By April 17th, contributors will regroup to identify remaining issues and finalize the roadmap for the release. The revised schedule is expected by April 22nd.
What This Means for WordPress Users
The delay of WordPress 7.0 serves as a reminder that large-scale features like real-time collaboration require extensive testing and refinement. For developers, this pause offers an opportunity to identify edge cases and provide meaningful feedback through nightly builds. Agencies and site owners relying on stability should hold off on upgrading test environments until the final release schedule is confirmed.
From an ecosystem perspective, this delay signals WordPress’s ongoing dedication to quality over speed. While the rollback to beta testing may seem inconvenient, it ultimately safeguards the platform’s reputation and ensures a smoother experience for users post-launch. For contributors, the clear guidelines outlined by project leadership enable focused efforts during this pause.
We recommend leveraging the WordPress Beta Tester plugin to stay updated on pre-release versions and actively participating in testing efforts. This collaboration is critical to ensuring the success of WordPress 7.0.
Frequently Asked Questions
What features are causing the delay in WordPress 7.0?
The real-time collaboration feature is the primary focus of the delay, alongside refinements to the Connectors admin screen.
How can I test the latest pre-release versions?
Install the WordPress Beta Tester plugin, select the “Bleeding edge” channel, and choose the “Nightlies” stream to access nightly builds.
Will the delay impact the timing of WordPress 7.1?
Yes, trunk commits for 7.1 are paused until further notice to prioritize stability for the 7.0 release.
Why are Release Candidate versions being treated as beta?
Technical limitations with versioning require RC versions to act as beta releases to ensure compatibility and minimize confusion.
When will the final WordPress 7.0 release schedule be announced?
A revised schedule will be published no later than April 22, 2026, following additional testing and contributor discussions.
