Commence: Operation WP 7.1

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

With the release of 7.0 earlier today, trunk is finally open to any and all commits for WordPress 7.1.

Trunktrunk 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. is now WordPress 7.1-alpha

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

Thank you to everyone for your continued patience.

Backporting to the numbered branches

As a reminder, the “double signoff” policy applies to changes being made to any numbered version branch. The dev-feedback commit keywords should be used to request a second committercommitter 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.’s review, with dev-reviewed being added after an additional signoff is given.

More information on this process can be found in the Make WordPress Core Handbook.

Props @jorbin, @audrasjb, @amykamala, @4thhubbard, @mosescursor for peer review.

#7-1