It was announced earlier this week that the final 7.0 release has been delayed specifically to allow more time to address testing feedback about the implementation of real-time collaboration. While the broad reasons for the delay were shared, this post will clarify what the delay means in practice (“returning to beta” after entering the Release…

WordPressCore's platform is a central hub for WordPress developers and contributors, offering insights into WordPress core development, plugin development, and theme customization. Through articles, tutorials, and community forums, WordPressCore offers insights into WordPress architecture, development best practices, and contributing to the WordPress open-source project. Readers can learn about WordPress coding standards, security guidelines, and performance optimization techniques to build powerful and secure websites with WordPress.

Make WordPress Core

WordPress 7.0 has been delayed beyond the Release Candidate phase to address real-time collaboration stability issues, an unprecedented step in the project's release history. The post outlines commit policies during the pause: trunk is closed for 7.1 work, backports to the 7.0 branch require double sign-off from two core committers, and only bug fixes for current-cycle regressions are allowed. Pre-release builds are paused until April 17th, with a new schedule to be published by April 22nd. A technical challenge around version numbering means releases will continue as RC3, RC4, etc., even though they function as betas, due to PHP's version_compare() limitations. String freeze remains in effect with limited exceptions for critical strings.

The Path Forward for WordPress 7.0