WordPress 7.2 Bug Scrub Schedule and Core Contributor Triage Guide

Introduction to WordPress 7.2 Release Preparedness

Preparing a major release of WordPress requires organized collaboration across a global network of open-source developers, testers, designers, and technical writers. As the release cycle for WordPress 7.2 progresses, systematic bug scrubs play a pivotal role in maintaining code stability, resolving regressions, and triaging reported defects. Bug scrubs provide a structured forum within the core contribution pipeline to systematically evaluate tickets, test patches, verify fixes, and ensure software quality before deployment.

To support the WordPress 7.2 development lifecycle, a structured schedule of twice-weekly bug scrubs has been established. Led primarily by core contributors @audrasjb and @im3dabasia1, these sessions move tickets through Trac workflow states. Whether evaluating early alpha enhancements or triaging high-priority regressions during the release candidate (RC) phase, understanding the scrub mechanics and schedule is essential for core contributors.

Alpha, Beta, and Release Candidate Bug Scrub Schedule

The scrub schedule for WordPress 7.2 is partitioned into three key phases of the release cycle: Alpha, Beta, and Release Candidate. Each phase carries specific strategic objectives, shifting focus from initial ticket evaluation to regression control and critical stability fixes.

Alpha Bug Scrubs Schedule

During the Alpha phase, scrubs address general tickets assigned to the WordPress 7.2 milestone, focusing on initial patch evaluations, early testing, and establishing ticket priority. Alpha scrubs occur twice weekly from mid-September through mid-October 2026:

• 15 September 2026 at 19:00 UTC — Led by @audrasjb
• 17 September 2026 at 16:00 UTC — Led by @im3dabasia1
• 22 September 2026 at 19:00 UTC — Led by @audrasjb
• 24 September 2026 at 16:00 UTC — Led by @im3dabasia1
• 29 September 2026 at 19:00 UTC — Led by @audrasjb
• 1 October 2026 at 16:00 UTC — Led by @im3dabasia1
• 6 October 2026 at 19:00 UTC — Led by @audrasjb
• 8 October 2026 at 16:00 UTC — Led by @im3dabasia1
• 13 October 2026 at 19:00 UTC — Led by @audrasjb
• 15 October 2026 at 16:00 UTC — Led by @im3dabasia1

Beta Bug Scrubs Schedule

Once WordPress 7.2 enters the Beta phase, the focus shifts sharply to issues reported from previous beta releases. Beta scrubs run from late October through mid-November 2026:

• 20 October 2026 at 19:00 UTC — Led by @audrasjb
• 22 October 2026 at 16:00 UTC — Led by @im3dabasia1
• 27 October 2026 at 19:00 UTC — Led by @audrasjb
• 29 October 2026 at 16:00 UTC — Led by @im3dabasia1
• 3 November 2026 at 19:00 UTC — Led by @audrasjb
• 5 November 2026 at 16:00 UTC — Led by @im3dabasia1
• 10 November 2026 at 19:00 UTC — Led by @audrasjb
• 12 November 2026 at 16:00 UTC — Led by @im3dabasia1

Release Candidate (RC) Bug Scrubs Schedule

The Release Candidate phase targets defects and regressions discovered in RC builds. At this point in the software development lifecycle, non-essential enhancements are deferred, and high-severity regressions receive maximum priority:

• 17 November 2026 at 19:00 UTC — Led by @audrasjb
• 19 November 2026 at 16:00 UTC — Led by @im3dabasia1
• 24 November 2026 at 19:00 UTC — Led by @audrasjb
• 26 November 2026 at 16:00 UTC — Led by @im3dabasia1
• 1 December 2026 at 19:00 UTC — Led by @audrasjb
• 3 December 2026 at 16:00 UTC — Led by @im3dabasia1
• 8 December 2026 at 19:00 UTC — Led by @audrasjb

Slack Operations and Real-Time Core Communication Channels

All core bug scrubs for WordPress 7.2 take place in real time within the official Make WordPress Slack workspace. Specifically, meetings are hosted in the #core channel. Contributors must register an account on Slack via the official Make WordPress registration portal (make.wordpress.org/chat/) to access the workspace.

In addition to organized bug scrubs, broader core development synchronization occurs weekly during the Core Development Meeting, held every Wednesday at 15:00 UTC in the #core channel. Participating in these text-based Slack sessions allows contributors to listen in, claim tickets for patch creation or testing, offer feedback, and coordinate directly with release leads.

Trac Report Triage: Utilizing Report 5 and Report 6

Trac serves as the official issue tracking database for WordPress core development. During bug scrubs, leads and participants rely on pre-configured Trac reports to isolate actionable tickets for the 7.2 release milestone:

• Trac Report 5: Displays a complete list of all open tickets assigned to the WordPress 7.2 milestone. Scrub leads utilize Report 5 to isolate highest-priority tickets and surface neglected tickets that require reproduction, testing, or feedback.
• Trac Report 6: Displays open WordPress 7.2 tickets organized systematically by workflow state. This report helps leads identify tickets stalled at specific stages, such as needs-patch, needs-testing, has-patch, or needs-dev-note.

By leveraging these targeted reports, participants ensure that time spent during the scrub directly addresses pipeline bottlenecks rather than unassigned or inactive requests.

Component-Specific Triage: Accessibility, Performance, and Test

While general bug scrubs cover all functional areas of core, specialized teams host recurring component scrubs and triage meetings to handle domain-specific challenges. These dedicated sessions run concurrently alongside the release-wide schedule:

• Accessibility Scrub: Meets every Tuesday at 16:00 UTC in the #accessibility Slack channel to triage screen reader support, keyboard navigation, and WCAG compliance issues.
• Performance Scrub: Meets every other Tuesday at 16:00 UTC in the #core-performance Slack channel to address database query optimizations, asset loading, web vitals, and execution benchmarks.
• Test Scrub: Meets on the 2nd and 4th Thursday of every month at 15:00 UTC in the #core-test Slack channel to manage automated test suites, end-to-end testing infrastructure, and unit testing coverage.

Component leads wishing to feature additional recurring component scrubs or triage sessions on the main schedule can request integration by contacting @audrasjb or @im3dabasia1 directly on Slack.

How to Lead a WordPress Core Bug Scrub

Leading a bug scrub is open to all community members regardless of prior technical leadership experience. Facilitating a scrub helps move stalled tickets forward and earns recognized contributor attribution ("props") in Dev Chat summaries and the official #props Slack channel.

To organize and lead an official or component-focused bug scrub, complete the following practical workflow:

1. Select Schedule and Scope: Determine the target date, UTC time, and specific subset of tickets or Trac report (e.g., Report 5, Report 6, or a designated component focus) you intend to scrub.
2. Notify Release Scrub Leads: Send a Slack message (ping) to @audrasjb or @im3dabasia1 detailing your proposed schedule and target scope so it can be integrated into the central 7.2 schedule.
3. Review Contribution Guidelines: Consult the Leading Bug Scrubs guide in the official WordPress Core Handbook for technical instructions on managing chat flow, updating Trac milestones, and applying workflow keywords.
4. Execute the Scrub: Conduct the live text session in #core or your designated component channel, updating ticket statuses, milestone tags, and key attributes in real time based on team consensus.

Core Bug Triage Principles and Contributor Best Practices

To maintain high standards across WordPress 7.2 development, triage participants adhere to standard definitions and workflow practices established by the core team:

• Defects vs. Enhancements: A bug (defect) represents an error, unexpected system behavior, or broken feature functionality. Performance improvements, feature refinements, and architectural refactoring are classified as enhancements or task requests.
• Prioritizing Regressions: Post-feature freeze, priority is given exclusively to regressions—adverse functional failures introduced relative to previous releases.
• Workflow Actions: During a scrub, ticket attributes are modified based on real-time verification. Common actions include confirming reproduction steps, requesting additional environment testing, marking verified patches for committer review, or reassigning milestone targets if a patch cannot land safely before release deadlines.

Primary reference: Review the original announcement for exact release details. This article is an independent explanation and does not reproduce the source text.