As WordPress 7.0 moves closer to its official release, the second phase of the Release Candidate (RC2) process brings critical updates for contributors and developers. This stage is pivotal for ensuring stability, translation readiness, and adherence to the established release policies.
Key Takeaways
- Core trunk is now open for WordPress 7.1-alpha commits, signaling the start of the next development cycle.
- Double sign-off is required for backporting production code to the WordPress 7.0 branch.
- Hard string freeze remains in effect, with exceptions available for critical strings approved by the Polyglots team.
- Only regressions and test suite expansions are allowed on the WordPress 7.0 milestone.
- Release squad coordination is critical for any last-minute changes during the freeze.
What’s New in the Release Candidate Phase?
The WordPress 7.0 RC2 phase introduces key procedural updates affecting both Core committers and non-committing contributors. One notable shift is the transition of the trunk branch to WordPress 7.1-alpha. This opens up the trunk for new commits tied to the next version, while WordPress 7.0 has been preserved in its own branch for final refinements.
Backporting Policies
Backporting production code to the 7.0 branch now requires stricter oversight. Contributors must secure double sign-off from two Core committers. This process ensures higher accountability and reduces the risk of introducing instability during the final stages of the release. The Trac keywords dev-feedback and dev-reviewed are now mandatory for tracking and approval. For developers accustomed to the more relaxed backporting process of earlier versions, this change underscores a tightened focus on quality control.
String Freeze Implications
The hard string freeze initiated with RC1 is still in effect. This freeze prevents the addition of new strings, with exceptions granted only for critical updates such as the About page. Existing strings can be removed or duplicated as needed, but contributors must seek guidance from Polyglots team reps for any strings reported as buggy. This policy emphasizes the importance of translation readiness, especially for WordPress’s global audience.
Remaining Milestone Tickets
Only two categories of tickets will be considered for the WordPress 7.0 milestone from this point forward:
- Regressions: Bugs introduced during the WordPress 7.0 development cycle, whether they affect existing features or new ones.
- Test Suite Expansions: Tests can be committed without restriction, ensuring robust coverage of new and existing features.
All other types of tickets will be deferred to future milestones. Contributors are advised to coordinate any proposed changes directly with the release squad via the #7-0-release-leads Slack channel.
What This Means for WordPress Users
For WordPress developers and agencies, the RC2 phase is a signal to finalize testing on sites that depend on WordPress 7.0 features. The hard string freeze means translation teams can move forward with localization efforts without risk of additional changes disrupting their workflows. If you’re a plugin or theme developer, this is your last opportunity to ensure compatibility with upcoming changes.
The double sign-off requirement for backporting also highlights a broader trend: WordPress Core is increasingly emphasizing accountability and stability during its release cycles. This benefits site owners and operators by reducing the likelihood of last-minute issues or regressions.
For contributors, the tightened policies may require better collaboration and adherence to Trac keywords. If you’re involved in Core development, leveraging proper communication channels and following these guidelines will be critical.
Frequently Asked Questions
What is the significance of the trunk transitioning to WordPress 7.1-alpha?
This transition marks the beginning of the next development cycle, allowing developers to start working on features and updates for WordPress 7.1 while the 7.0 branch is finalized.
How does the double sign-off policy for backporting affect contributors?
It requires contributors to secure approval from two Core committers, adding an extra layer of review to ensure quality and minimize risks of instability.
What should plugin and theme developers do during the RC2 phase?
They should focus on testing their products against WordPress 7.0 to ensure compatibility and address any regressions or issues before the final release.
Can new strings still be added to WordPress 7.0?
No, except for critical strings like the About page, which require approval and proper tagging for translation team coordination.
