WordPress 7.0 has officially entered the Release Candidate (RC) phase, signaling that the next major update to the world’s most popular content management system is nearing its final release. While RC phases are routine in software development, WordPress 7.0 introduces several procedural changes and technical hurdles that developers, contributors, and site operators should be aware of.
Key Takeaways
- WordPress 7.0’s Release Candidate phase requires double sign-off for commits to trunk until the 7.0 branch is created.
- The hard string freeze is in effect, delaying translation efforts until RC2 later this week.
- Only regressions and test suite expansions can be placed on the 7.0 milestone going forward.
- Trunk will move to 7.1-alpha after the 7.0 branch is finalized.
Double Sign-Off Requirements for Commits
One of the most immediate changes introduced in the WordPress 7.0 RC phase is the requirement for double sign-off on all commits to trunk. This procedural adjustment stems from a technical issue that has delayed the creation of the 7.0 branch until RC2, later this week. According to the Make WordPress Core announcement, committers must use the dev-feedback keyword to request a second review, and the dev-reviewed keyword once the commit has been approved by two core committers.
Commits related to the test suite are exempt from this double sign-off requirement, allowing for continued expansion of testing coverage during this critical phase. In practice, this policy aims to reduce the risk of regressions or critical issues slipping through in the absence of a finalized branch.
Hard String Freeze and Translation Delays
Another notable update is the implementation of a hard string freeze, a standard practice during RC1 releases. Normally, this would enable the Polyglots team to begin translating strings for the upcoming release into various languages. However, the delayed creation of the 7.0 branch means that translation efforts cannot commence until RC2. This delay could impact multilingual site operators and plugin authors who rely on timely translations to support their user bases.
Despite the delay, the usual rules for hard string freeze remain in place. No new strings will be added, although exceptions can be made for critical elements like the About page, provided they are tagged with the i18n-change keyword in Trac and communicated to the Polyglots team. Contributors are also advised to report any buggy strings—those that cannot be translated into all languages effectively—for further guidance.
Restricted Ticket Types for WordPress 7.0
As WordPress 7.0 enters its final stretch, only two types of tickets are allowed on the 7.0 milestone: regressions and test suite expansions. Regressions refer to bugs introduced during the current development cycle, whether they affect existing features or new ones. Test suite expansions, which are unaffected by code or string freezes, can continue to be committed freely to enhance testing coverage.
This restriction underscores the focus on stability and quality assurance as the release date approaches. Developers with outstanding feature-related tickets will need to push those items to the next version cycle, beginning with 7.1-alpha.
What This Means for WordPress Users
For developers and contributors, the procedural adjustments during WordPress 7.0 RC highlight the importance of adhering to stricter guidelines as the release nears completion. If you’re actively working on trunk commits, double-check that your changes meet the milestone criteria and secure the required approvals to avoid delays.
Site owners and operators should anticipate potential delays in translations for plugins or themes due to the postponed branch creation. Multilingual sites may face challenges if language strings are not available in time for the final release. We recommend monitoring updates from the Polyglots team for progress on translation availability.
Overall, WordPress 7.0 is shaping up to be a critical release, with procedural safeguards that prioritize stability over speed. Plugin authors should focus on regression fixes and test suite improvements, while agencies should prepare for a smooth transition once 7.0 rolls out.
Frequently Asked Questions
What is the significance of the hard string freeze?
The hard string freeze ensures that no new strings are added, allowing translation teams to focus on completing language packs for the release. However, translations are delayed until the 7.0 branch is created.
Why are commits to trunk requiring double sign-off?
This policy reduces the risk of regressions or critical errors by ensuring that two core committers review and approve changes until the 7.0 branch is finalized.
What types of tickets can remain on the 7.0 milestone?
Only regressions and test suite expansions are permitted on the 7.0 milestone, emphasizing stability and testing over new features.
When will trunk move to 7.1-alpha?
Trunk will transition to 7.1-alpha after the 7.0 branch is created, following RC2 later this week.
