{"id":123435,"date":"2026-05-20T19:22:03","date_gmt":"2026-05-20T19:22:03","guid":{"rendered":"https:\/\/make.wordpress.org\/core\/?p=123435"},"modified":"2026-05-20T19:22:03","modified_gmt":"2026-05-20T19:22:03","slug":"commence-operation-wp-7-1","status":"publish","type":"post","link":"https:\/\/make.wordpress.org\/core\/2026\/05\/20\/commence-operation-wp-7-1\/","title":{"rendered":"Commence: Operation WP 7.1"},"content":{"rendered":"

With the release of 7.0 earlier today, trunk<\/code> is finally open to any and all commits for WordPress 7.1.<\/p>\n\n\n\n

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> is now WordPress 7.1-alpha<\/h2>\n\n\n\n

While the common practice is for trunk<\/code> to open once the next release has been branched<\/a>, closing the primary 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> to any commits unrelated to 7.0 was necessary to avoid making it more complicated to add, modify, or remove features<\/a> from the release during the extension to the cycle<\/a> to evaluate the state and readiness of the Real-time collaboration feature.<\/p>\n\n\n\n

Thank you to everyone for your continued patience.<\/p>\n\n\n\n

Backporting to the numbered branches<\/h2>\n\n\n\n

As a reminder, the \u201cdouble signoff\u201d policy applies to changes being made to any numbered version branch. The dev-feedback commit<\/code> keywords 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, with dev-reviewed<\/code> being added after an additional signoff is given.<\/p>\n\n\n\n

More information on this process can be found in the Make WordPress Core Handbook<\/a>.<\/p>\n\n\n\n

Props @<\/span>jorbin<\/a>, <\/em>@<\/span>audrasjb<\/a>, <\/em>@<\/span>amykamala<\/a>, @<\/span>4thhubbard<\/a>, @<\/span>mosescursor<\/a> for peer review.<\/em><\/p>\n

#<\/span>7-1<\/a><\/p>