Skip to content
← Blog
Search and websites ·

WordPress 7.2 closes out 2026. Plan your testing for December.

WordPress 7.2 is the last major release of 2026 and brings a new default theme, with Beta 1 due in late October and the final release on 8 to 10 December.

Agency desk with a laptop, a staging screen and a December calendar, ready for testing WordPress 7.2 updates

The planning page for WordPress 7.2 on Make WordPress Core, dated 12 February 2026, names the release squad and confirms that 7.2 will be the final major release of 2026. A new default theme ships alongside it, and Gutenberg Times reports that Beta 1 is scheduled for 20 to 22 October, with the final release set for 8 to 10 December.

If you look after sites for clients or members, those two windows shape your autumn: testing in late October, live updates in December.

What the planning page confirms

Matt Mullenweg is the Release Lead, the community member ultimately responsible for the release. David Baumwald leads release coordination. George Mamadashvili and Peter Wilson are the tech leads. The triage leads are Jb Audras and Eshaan Dabasiya, and the test leads are Md Noruzzaman, Jina Parekh and Erick Wambua.

The default theme is the part your clients and members will see, so its leads are worth knowing. Henrique Iamarino leads design; Maggie Cabrera and Carolina Nymark lead development.

On features, the page says little. New features will be considered for 7.2 if they're deemed reasonably ready, and all release decisions are the release team's to make and communicate, with input gathered from the community. The page doesn't name the new theme or list planned features. Our advice follows from that: don't promise anyone a specific 7.2 feature until it's in a release.

How firm are the dates?

The schedule section on the planning page is empty, which is why the October and December windows come from Gutenberg Times. The planning page does say that patches for enhancements won't be committed after the scheduled dates, so that focus can go to fixing bugs. After feature freeze, only bugs are dealt with, and regressions are the highest priority.

The WordPress.org roadmap says new features are frozen a month before a release, with focus shifting entirely to quality and performance. It also says projected dates are for rough planning only. Treat December as a window that can move.

The roadmap's 2026 goals include three major releases. Phase 3 of the Gutenberg project is underway, centred on collaborative editing and workflows.

There's one update to handle first. WordPress 7.1.1 is a bug-fix-only release covering 16 Core tickets and 22 Gutenberg pull requests, co-led by Adam Silverstein, Adrian Duffell and Andra Ganescu. RC1 is out, and the final release was scheduled for Thursday 17 September. Get every site you manage onto it before you test 7.2: anything that breaks can then be traced to the new release. If 7.1 gave you trouble, the release retrospective takes feedback until 30 September, and submissions are anonymised in the follow-up summary.

What should you do before December?

The staging test matters most. Put it in your diary for the week after Beta 1. Run a staging copy of each client or member site on the beta and check the theme, the plugins each site relies on, and any forms or checkout pages. Don't test on live sites.

Read the dev notes as they appear. They're published on the Make/Core blog during the beta phase, then gathered into a Field Guide at the start of the release candidate phase. The Field Guide is the one document to check before you update anything live.

Some work in progress is worth watching without passing it on to clients yet. Gutenberg Times reports a plan from Anne McCarthy to fix the discoverability problems in Notes by Beta 1. It includes a more visible spot in the block toolbar, a suggestion mode, Notes opening alongside the Settings sidebar, and emoji reactions. In her words, "Notes are hard to discover, cumbersome to use, and tricky to track where and when they are left."

If you run shops, check PHP versions. A separate proposal from Brian Coords would require PHP 8.1 or newer from WooCommerce 11.5, targeted for January 2027. Ask your hosts which version each shop runs and when they can move it.

If testing turns up a fault, you can report it. The planning page invites contributors to pick a 7.2 ticket on Trac, with the Core Contributor Handbook for help. Weekly meetings run in the #core Slack channel every Wednesday at 15:00 UTC.

Written with AI by Corantr Media Desk from its sources' facts, checked claim by claim, and approved by a person before it was published. How we write.

More from the blog