WordPress 7.0 Release Candidate Phase ![rw-book-cover](https://s.w.org/images/home/wordpress-default-ogimage.png) Now that WordPress 7.0 has [entered the Release Candidate phase](https://wordpress.org/news/2026/03/wordpress-7-0-release-candidate-1/), the following policies are in place. *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.* #### Committing to Trunk Due to a technical issue that must be resolved before the `7.0` branch is created, branching has been delayed until RC2 later this week (see and the [relevant pull request](https://github.com/WordPress/wordpress-develop/pull/11064) for background on the issue). **As a result, all commits to `trunk` will require double sign-off by two core committers until the `7.0` branch is created.** The `dev-feedback` keyword should be used to request a second committer’s review, `dev-reviewed` 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. #### String Freeze RC1 release marks the hard string freeze point of the release cycle. While this normally means the Polyglots team 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 translation until the `7.0` branch is created.** Despite this, the normal rules for hard string freeze will be followed: * No new strings are permitted. Exceptions can be made for critical strings (the About page, for example) provided they are properly tagged with the `i18n-change` keyword in Trac and the Polyglot team is made aware. * Existing strings can be removed and/or duplicated if needed. Seek guidance from the [Polyglots team reps](https://make.wordpress.org/updates/team-reps/) for any strings reported as buggy. A buggy string is one that can not be translated to all languages in its current form. #### Tickets on the WordPress 7.0 milestone For the remainder of the cycle, only two types of tickets may be placed on/remain on the [7.0 milestone](https://core.trac.wordpress.org/tickets/major): * **Regressions**: bugs that have been introduced during the WordPress 7.0 development cycle, either to existing or new features. * **Test suite expansion**: tests can be committed at any time without regard to code or string freezes. This can cover either new or existing features. #### Bumping Trunk to WordPress 7.1-alpha After the `7.0` branch is created following RC2, a follow-up post will be published announcing that `trunk` is open for commits related to the next version of the software., WordPress 7.0 Release Candidate Phase, make.wordpress.org, 01kmjjg0fkk9d154gkdsc927rv.