{"id":122231,"date":"2026-03-25T03:27:17","date_gmt":"2026-03-25T03:27:17","guid":{"rendered":"https:\/\/make.wordpress.org\/core\/?p=122231"},"modified":"2026-03-27T17:10:46","modified_gmt":"2026-03-27T17:10:46","slug":"wordpress-7-0-release-candidate-phase","status":"publish","type":"post","link":"https:\/\/make.wordpress.org\/core\/2026\/03\/25\/wordpress-7-0-release-candidate-phase\/","title":{"rendered":"WordPress 7.0 Release Candidate Phase"},"content":{"rendered":"
\n
<\/div>\n
\n

Note:<\/strong> The 7.0 branchbranch<\/span> A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a \"branch\", such as \"the 4.0 branch\".<\/span><\/span><\/span> was created on 26 March. This post should be considered obsolete for the RCrelease candidate<\/span> One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta)<\/a>.<\/span><\/span><\/span> phase of the 7.0 release cycle. Refer to the updated post<\/a> for expectations and policies in place.<\/p>\n<\/div><\/div>\n\n\n\n

Now that WordPress 7.0 has entered the Release Candidate phase<\/a>, the following policies are in place.<\/p>\n\n\n\n

These policies mainly cover how and when CoreCore<\/span> Core is the set of software required to run WordPress. The Core Development Team builds WordPress.<\/span><\/span><\/span> committers can commit. For non-committing contributors, this post may help explain why Core committers make certain decisions.<\/em><\/p>\n\n\n\n

Committing to Trunktrunk<\/span> A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running \"trunk\", then you are on the latest revision.<\/span><\/span><\/span><\/h2>\n\n\n\n

As a result, all commits to trunk<\/code> will require double sign-off by two core committers until the 7.0<\/code> branch is created.<\/strong><\/p>\n\n\n\n

The dev-feedback<\/code> keyword should be used to request a second committercommitter<\/span> A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and\/or for a specific component.<\/span><\/span><\/span>\u2019s review, dev-reviewed<\/code> should be added to indicate a second committer has reviewed and approved the commit to the 7.0 branch. Commits to the test suite do not require double sign-off.<\/p>\n\n\n\n

String Freeze<\/h2>\n\n\n\n

RC1 release marks the hard string freeze point of the release cycle. While this normally means the Polyglots teamPolyglots Team<\/span> Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https:\/\/make.wordpress.org\/polyglots\/teams\/<\/a><\/span><\/span><\/span> can begin translating strings from the upcoming release into their local language, a version-specific branch is required. As a result, strings will not be available for translationtranslation<\/span> The process (or result) of changing text, words, and display formatting to support another language. Also see localization<\/a>, internationalization<\/a>.<\/span><\/span><\/span> until the 7.0<\/code> branch is created.<\/strong><\/p>\n\n\n\n

Despite this, the normal rules for hard string freeze will be followed:<\/p>\n\n\n\n

Due to a technical issue that must be resolved before the 7.0<\/code> branch is created, branching has been delayed until RC2 later this week (see #64393<\/a> and the relevant pull request<\/a> for background on the issue).<\/p>\n\n\n\n