{"id":12688,"date":"2026-10-01T14:56:14","date_gmt":"2026-10-01T14:56:14","guid":{"rendered":"https:\/\/make.wordpress.org\/test\/?p=12688"},"modified":"2026-10-01T14:56:14","modified_gmt":"2026-10-01T14:56:14","slug":"test-scrub-schedule-for-wordpress-7-2","status":"publish","type":"post","link":"https:\/\/make.wordpress.org\/test\/2026\/10\/01\/test-scrub-schedule-for-wordpress-7-2\/","title":{"rendered":"Test Scrub Schedule for WordPress 7.2"},"content":{"rendered":"

As most of you already know, WordPress 7.2<\/a> is set to be the final major releaseMajor Release<\/span> A set of releases or versions having the same major version number may be collectively referred to as \u201cX.Y\u201d -- 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.<\/span><\/span><\/span> of 2026, currently targeted for December 8, 2026<\/strong>. As we gear up for this key milestone, our Test team will be switching things up a little.<\/p>\n\n\n\n

Starting with our next weekly Patch Testing Session<\/a>, we\u2019ll be running a Test Scrub<\/strong> 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\u2019s a solid way to get hands-on with a major release and help shape what ships.<\/p>\n\n\n\n

Test Scrub in Place of Patch Testing Sessions<\/h3>\n\n\n\n

From our next scheduled session onward, Test Scrubs will run on the 2nd and 4th Thursday of each month at 3:00 PM UTC<\/a><\/strong>. These sessions will focus specifically on WordPress 7.2 milestone tickets.<\/p>\n\n\n\n

Where Will It Happen?<\/h2>\n\n\n\n

Each Test Scrub takes place in the #core-test<\/a> channel on the Make WordPress SlackSlack<\/span> Slack is a Collaborative Group Chat Platform https:\/\/slack.com\/<\/a>. The WordPress community has its own Slack Channel at https:\/\/make.wordpress.org\/chat\/<\/a><\/span><\/span><\/span>, at the same time as our regular weekly Test team meetings. If any additional release-focused scrubs get scheduled, they\u2019ll be announced in the same channel as well and added to the meetings calendar.<\/p>\n\n\n\n

What Tickets Will We Focus On?<\/h2>\n\n\n\n

The main focus will be tickets tagged Has Patch<\/strong> or Needs Testing<\/strong> against the 7.2 milestone. You can pull these up directly from the 7.2 report on Trac<\/a>. As the release progresses through BetaBeta<\/span> 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.<\/span><\/span><\/span> and RCRelease Candidate<\/span> A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.<\/span><\/span><\/span>, we\u2019ll also shift attention toward key features and regressions that need dedicated testing.<\/p>\n\n\n\n

Interested in Leading a Test Scrub?<\/strong><\/p>\n\n\n\n

Did you know anyone can lead a Test Scrub, any time? That includes you.<\/p>\n\n\n\n

If you\u2019d like to run one, reach out in the #core-test<\/a> Slack channel with:<\/p>\n\n\n\n