This updates the expectations and policies that should be followed through the final release of WordPress 7.0 following the previous post and the release of RC2 on 26 March. These policies mainly cover how and when Core committers can commit. For non-committing contributors, this post may help explain why Core committers make certain decisions. Trunk…

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 entered its second release candidate phase. Trunk is now open for WordPress 7.1-alpha development. Backporting production code to the 7.0 branch now requires double sign-off from two core committers. A hard string freeze is in effect since RC1, with only critical exceptions allowed using the i18n-change keyword. For the remainder of the cycle, only regression fixes and test suite expansions may be added to the 7.0 milestone.

WordPress 7.0 Release Candidate Phase, Pt. 2