WordPress 7.1.0 was released August 19, 2026. While the work of a major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. team includes people filling many different positions, maintenance release teams generally are considerably smaller, often 1–3 people. Minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. managers are responsible for:

• Triaging bugs in coordination with committers and component maintainers.
• Drafting announcements for the release.
• Preparing for and running release day activities.
• Updating the documentation on minor releases so that it gets better each time.

Members of the 7.1 release cohort are encouraged to stay on as release managers for maintenance releases, but it is not required to have been on a major release squad in order to be on a minor release team.

WordPress 7.1.1 will be scheduled based upon the severityseverity The seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs. and quantity of bugs reported with a guesstimated release date between 1 September and 24 September. Please keep this timeline in mind when volunteering to be a release manager.

If you are interested in volunteering to be a release manager for the 7.1.x maintenance releases, please comment on this post or message me directly no later than 28 August.

Props to @joemcgill, @annezazu, @jeffpaul for reviewing this post before publication.

#7-1, #7-1-1, #7-1-x, #maintenance