WordPress 7.2 Release Squad: Matt Mullenweg Returns as Lead

Every release cycle I have watched over the last decade has a moment that tells you what the project actually thinks about itself. The 7.2 squad announcement, published yesterday, is that moment for this cycle. Not because of any single name on the list — because of the shape of the list itself.

The squad is smaller than the last few. It leans on the Make team representatives to plug the gaps instead of appointing a component owner for everything. And the release lead line reads: Matt Mullenweg. A founder taking the release-lead seat, on a release scheduled to ship the last major of 2026, on top of a fresh Twenty Twenty-Seven default theme. That is a signal, and it is worth reading carefully before assuming what it means.

I have been in enough enterprise builds — London clients on Monday, Istanbul on Tuesday, Bratislava on Wednesday — to know that “small squad, big scope” either produces a very tight release or a very late one. Nothing in between. Here is what actually landed, and what I would do about it.

What is actually new

On September 9, 2026, the Core team announced the WordPress 7.2 release squad. Matt Mullenweg is release lead. David Baumwald handles release coordination. Tech leads are George Mamadashvili and Peter Wilson. Triage is Jb Audras and Eshaan Dabasiya. Test leads are Md Noruzzaman, Jina Parekh, and Erick Wambua.

The default theme squad is broken out separately for this cycle: Henrique Iamarino leads design on Twenty Twenty-Seven, with Maggie Cabrera and Carolina Nymark as dev leads and Juanfra Aldasoro as mentor lead. The announcement is explicit about the trade-off: this is a “smaller, focused” squad, and gaps that used to be filled by named component leads are now handled by working directly with Make team representatives. The post also notes the number of volunteers “far exceeded the available squad roles” — so the smaller shape is a choice, not a shortage.

The dates on the 7.2 milestone page are firm. Beta 1 is scheduled for October 20–22, 2026. RC 1 is November 17–19. General release is December 8–10, with a dry run and a 24-hour code freeze the day before. 7.2 is the final major of 2026.

Two supporting posts landed on the same day. The bug scrub schedule, coordinated by Jb Audras and Eshaan Dabasiya, runs twice-weekly from September 15 through December 8: alpha scrubs at alternating 19:00 and 16:00 UTC, then beta scrubs from October 20, then RC scrubs from November 17. And the toolchain moved: Node.js 24.x (minimum 24.18.0) and npm 11.x (minimum 11.16.0) are now required for trunk and the 7.1 branch in both wordpress-develop and gutenberg. Older branches keep the previous floor (Node 20.10, npm 10.2.3). Node 26 is already on the roadmap for October when it reaches Active LTS.

And in the background, the 7.1 “Mary Lou” retrospective is open for feedback through September 30, 2026 — worth filling in if you shipped anything on 7.1 that hurt.

Why it matters for WordPress and WooCommerce people

Three things follow from this announcement, and they are not the ones the trade press will lead with.

First, the schedule is tight. Beta 1 in six weeks, RC in nine, ship in thirteen. On a release that also has to deliver a brand-new default theme. If your product depends on core in any meaningful way — a WooCommerce extension, a block plugin, a page builder — you have a hard planning constraint. Beta lands the same week Chrome pushes a stable, right in the middle of Q4 e-commerce freeze windows for most retail clients. Plan your compatibility work around that, not around a hoped-for slip.

Second, the “smaller squad, lean on Make reps” model changes how you get triage attention. If you have historically pinged a named component lead for a bug in your area, that path may not exist this cycle. The intended route is through the Make team for that component. If your team does not know its team reps, this is the week to find them.

Third, the founder-as-release-lead line. I am not going to read tea leaves on why. What I will say is that the last time we had this level of top-down focus on a release, quality-of-life work — the boring, unglamorous stuff — landed better than any single headline feature. If that pattern holds, 7.2 will be the release where a lot of small edges get sanded off, alongside the new theme. That is a good release to plan around, not a bad one.

For WooCommerce agencies specifically: 7.2 GA lands December 8–10. WooCommerce’s own cadence is monthly. That means a Woo release around the 7.2 GA window and another one in early January. Do the math on your Q4 code freezes before you promise a client a mid-December deploy.

What I would do about it

Four moves, in order.

Move one: put October 20 in the calendar as your beta 1 test date. Not “when I get around to it.” A booked hour, on the day, with a fresh Playground instance and your top three client sites cloned into it. If you catch a regression in beta 1, you have five weeks to file a Trac ticket and see it fixed. If you catch it at RC, you are hoping for a point release.

Move two: bump your local toolchain now. Node 24.18 and npm 11.16 are not optional for contributing anymore, and if you build blocks or plugins from source, running your CI on the same versions core runs on is the cheapest form of insurance you can buy. On a Mac, nvm install 24.18 && nvm use 24.18 is a two-minute job. Do it before your next feature branch, not after your CI turns red at 11 pm.

Move three: if you or a client have shipped anything meaningful on 7.1 — collaborative editing outreach, the new blocks, iframed editor changes — file the retrospective form before September 30. This is the release cycle’s only structured feedback channel. Complaints filed into a Slack void do not change process. A completed form does.

Move four: freeze your Q4 deploy windows around the December 8–10 GA date. Not on top of it. I have shipped enough December launches in twenty-plus years — from CorelDRAW-era brochure sites through Flash portals to today’s headless Woo builds — to know that the last major of the year is the one clients most want to deploy against, and the one you most want a week of daylight after. Ship your holiday build on 7.1.1 in November, or wait until the January point release settles. Do not ship into the release week itself.

The 7.2 squad is small, the schedule is tight, and the founder is holding the release-lead pen. Read that as focus, plan accordingly, and get your test rig running before the beta lands.