WordPress 7.1.1 Maintenance Release Schedule and Core Workflow Guide

Overview of the WordPress 7.1.1 Maintenance Release

Following the major release of WordPress 7.1, core contributors and community maintainers have actively monitored reports across official channels, including the WordPress.org Support Forums, Core Trac, and the Gutenberg GitHub repository. Due to the volume and severity of incoming technical tickets, the core development team initiated the schedule for WordPress 7.1.1 as a dedicated, bug-fix-only maintenance release.

Maintenance releases in the WordPress core lifecycle address issues introduced during recent feature releases (regressions) or resolve minor defects that were intentionally deferred during the prior release freeze. By isolating fixes to non-feature adjustments, the engineering effort maintains core system stability while ensuring backward compatibility across diverse hosting environments and plugin ecosystems.

Release Leadership and Communication Channels

The preparation and execution of WordPress 7.1.1 are co-led by experienced core contributors:

• @adamsilverstein
• @adrianduffell
• @andraganescu

Release announcement documentation was reviewed prior to publication by @jorbin and @adrianduffell. Technical discussions and real-time coordination are divided across specific Slack channels within the official WordPress workspace:

• General Core Development & Code Decisions: The #core channel hosts scheduled bug scrubs and technical evaluation of patches. Standard core development meetings also take place in this room every Wednesday at 15:00 UTC.
• Release Leads Coordination: Operational planning, timing adjustments, and release candidate decisions take place in the dedicated 7.1 Release Leads room.

WordPress 7.1.1 Full Timeline and Schedule Breakdown

The schedule for WordPress 7.1.1 spans targeted bug scrubs, a release candidate milestone, opening of the subsequent maintenance milestone, and the final general release. Note that published times serve as estimates and depend on release lead availability and technical consensus during testing.

Targeted Fix Scope and Maintenance Criteria

WordPress 7.1.1 is strictly structured as a maintenance update rather than an enhancement release. To qualify for inclusion in 7.1.1, a bug ticket must meet specific criteria:

• Regressions: Defects directly introduced during the WordPress 7.1 development or release cycle. These are assigned the highest priority to prevent systemic degradation.
• Deferred Fixes: Tickets that were deliberately postponed during the late stages of the 7.1 release cycle to allow further testing without risking release stability.

Performance enhancements, feature expansions, and architectural refactoring are excluded from maintenance releases and are deferred to future major releases or minor feature cycles.

Tracking Issues Across Trac and the Gutenberg Repository

Because modern WordPress combines PHP core services with a modern JavaScript block editor, issue tracking for maintenance updates spans two primary platforms:

• Core Trac (Trac Report 4): Used to track PHP core, database, REST API, administration screens, and infrastructure bugs. Contributors monitor Report 4 for open 7.1.x maintenance candidates.
• Gutenberg GitHub Repository (7.1.x Editor Tasks Board): Used for tracking block editor bugs, component regressions, and block interface fixes slated for backporting into the minor release.

Tickets listed in these locations must undergo code review, unit test verification, and cross-browser testing before being merged into the 7.1 core branch.

The Role of Bug Scrubs in Release Preparation

Bug scrubs are structured real-time sessions held in the #core Slack channel. During a scrub, contributors review open tickets under the active milestone to ensure each issue is moving toward resolution.

Key activities performed during a bug scrub include:

• Triage and Severity Assessment: Evaluating incoming reports from Support Forums, Trac, and GitHub to judge impact and urgency.
• Patch Review: Testing attached patches, reviewing code quality, and verifying inline documentation.
• Milestone Management: Determining whether a ticket can be completed before RC1. On September 8, 2026, the 7.1.2 milestone opens, allowing leads to punt tickets that are not ready for 7.1.1 to the 7.1.2 pipeline.
• Self-Directed Scrubs: Community members and agency teams are encouraged to run local or independent scrubs to test patches and provide feedback ahead of official meetings.

Release Candidate (RC1) and General Deployment Protocols

The progression from development to public distribution follows a precise sequence designed to prevent breaking changes on production sites:

• Release Candidate 1 (RC1): Scheduled for September 10, 2026 at 17:30 UTC. RC1 represents a feature-complete snapshot of 7.1.1. It signals to plugin developers, theme authors, hosting providers, and site administrators that the codebase is ready for integration testing.
• String Freeze and Translations: When RC1 is released, localized strings are finalized. Polyglot teams across various locales begin translating updated or introduced strings to ensure full localization coverage upon release.
• General Release: Scheduled for September 17, 2026 at 15:00 UTC. Once final testing and post-RC1 scrubs (such as the September 15 session) confirm stability, WordPress 7.1.1 is pushed live to auto-update channels and download servers worldwide.

How Developers and Maintainers Can Participate

Contributions to the 7.1.1 maintenance release are open to all WordPress developers and site maintainers. Key ways to contribute include:

• Testing Patches: Applying proposed patches from Trac Report 4 or GitHub PRs to local testing environments and posting confirmation or reproduction steps.
• Participating in Slack Scrubs: Joining the scheduled #core meetings to offer technical insights, verify patch stability, or help scrub backlogged tickets.
• Translating Strings: Assisting translation teams in localized environments to ensure 100% completion of new or modified core strings.
• Reporting Regressions: Submitting detailed bug reports with exact steps to reproduce, server environment specifics, and expected vs. actual behavior on WordPress Trac.

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