As most of you already know, WordPress 7.2 is set to be the final major release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality. of 2026, currently targeted for December 8, 2026. As we gear up for this key milestone, our Test team will be switching things up a little.
Starting with our next weekly Patch Testing Session, we’ll be running a Test Scrub dedicated to WP 7.2 in place of the usual Future Milestone Tickets session. These scrubs will center on tickets and issues tied to the 7.2 milestone specifically. It’s a solid way to get hands-on with a major release and help shape what ships.
Test Scrub in Place of Patch Testing Sessions
From our next scheduled session onward, Test Scrubs will run on the 2nd and 4th Thursday of each month at 3:00 PM UTC. These sessions will focus specifically on WordPress 7.2 milestone tickets.
Where Will It Happen?
Each Test Scrub takes place in the #core-test channel on the Make WordPress Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/, at the same time as our regular weekly Test team meetings. If any additional release-focused scrubs get scheduled, they’ll be announced in the same channel as well and added to the meetings calendar.
What Tickets Will We Focus On?
The main focus will be tickets tagged Has Patch or Needs Testing against the 7.2 milestone. You can pull these up directly from the 7.2 report on Trac. As the release progresses through Beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. and RC A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge., we’ll also shift attention toward key features and regressions that need dedicated testing.
Interested in Leading a Test Scrub?
Did you know anyone can lead a Test Scrub, any time? That includes you.
If you’d like to run one, reach out in the #core-test Slack channel with:
- The day and time you have in mind
- The report or tickets you’d like to focus on (a specific Trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. report, a feature area, or a Beta/RC build, for example)
If your scrub is specifically focused on WordPress 7.2, even better — let us know and we’ll add it to the schedule so the rest of the team knows to join in. Leading a scrub is one of the most direct ways to contribute.
Let’s Contribute Together
This is a great opportunity to get involved with the WordPress 7.2 release, learn more about how the release process works, and help ensure the overall quality and stability of WordPress. Every contribution counts, so come join us for the Test Scrub sessions and be part of this release.
Thank You ❤️
Thanks to everyone who contributes time, testing, feedback, and expertise — community testing is a key part of what makes every WordPress release successful.
Let’s work together to make WordPress 7.2 a smooth and high-quality release.
Props to @r1k0, @huzaifaalmesbah, @noruzzaman for pre-publish review.
