Planning for the WordPress 7.1 Release has started, and if you’ve followed core development since the 6.x days, the way it’s being run looks different. The big multi-lead squads are gone. This cycle has a smaller Release Squad, and the proposed final release date is Wednesday, August 19, 2026, lined up with WordCamp US.
On large WordPress projects I’ve managed, “too many cooks” has been a real bottleneck, and release squads had the same problem. They got bloated, and the communication overhead held up decisions that needed to be made quickly. Trimming the squad for the WordPress 7.1 Release is a practical call: it works with the Make Team Reps instead of duplicating what they already do, which means less friction between core contributors and the release leads.
The WordPress 7.1 release schedule
The timeline is tight, but it’s laid out clearly. We’re in the Alpha phase now, which started back in March. If you build plugins that hook deep into core, start testing against trunk now. These are the milestones to watch:
| Milestone | Target Date |
|---|---|
| Beta 1 | July 15, 2026 |
| Beta 2 | July 22, 2026 |
| Release Candidate 1 | August 5, 2026 |
| Final Release | August 19, 2026 |
I’ve watched plenty of “final” dates move. Remember the WordPress 7.0 release date shift? The project has always been flexible about dates. What the squad wants to avoid is late-cycle surprises, the kind that end in rushed hotfixes or Transient cache problems on high-traffic sites.
How to test WordPress 7.1 alpha safely
Don’t wait for the official beta to find out what breaks. If you have a staging environment (and you should), WP-CLI will get you onto the alpha in two commands. It’s the easiest way to spot Race Conditions or deprecated function warnings before they reach production.
# Update to the latest nightly/alpha version
wp core update --version=7.1-alpha --force
# Verify the version
wp core versionIf you run enterprise WooCommerce builds, test early. While you’re at it, read the performance notes from 7.0 and check whether any of the older regressions got fixed this cycle.
The call for technical leads
The project is looking for volunteers for roles like Tech Leads, Triage Leads, and Release Coordinators, and these roles come with real work. Tech Leads, for example, oversee the actual code merges and triage Gutenberg features. It’s a lot, but if you want to know wp-settings.php or the WP_Query internals in detail, being on the squad is the fastest way to learn them.
You don’t have to travel to WCUS. All coordination happens in the #core and #7-1-release-leads Slack channels. If you can guide contributors and shepherd patches through, think about volunteering before the June 5th deadline in the official handbook.
If keeping up with the WordPress 7.1 Release is eating your dev hours, or you’re not sure how the core changes will hit your custom stack, I can take that off your plate. I’ve been working with WordPress since the 4.x days.
The practical takeaway
The smaller squad for the WordPress 7.1 Release shows the project tightening up how it organizes itself. Fewer people in the loop should mean faster triage and steadier releases. Developers: put your local environment on 7.1-alpha today. Business owners: plan a maintenance window for late August, and make sure nobody on your team gets caught off guard by trunk on launch day.
