WordPress 7.1.1 Release Schedule  🔗 **Source:** [WordPress 7.1.1 Release Schedule](https://make.wordpress.org/core/2026/09/02/wordpress-7-1-1-release-schedule/) > [!note]+ Document Notes > --- > tags: [wordpress-core, wordpress-7-1, minor-release, release-schedule, bug-scrub, make-wordpress-core, release-coordination, trac, gutenberg, wordpress-release-process, adam-silverstein] > author: Adam Silverstein > source: make.wordpress.org > reference: https://make.wordpress.org/core/2026/09/02/wordpress-7-1-1-release-schedule/ > date created: 2026-09-02 09:10 > --- > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > [!warning] Thin source — 231 words, six paragraphs and one table > > A scheduling post on Make/Core, published 2026-09-02 05:00 UTC. Byline (Adam Silverstein) taken from the live page's `entry-author` element; Reader metadata recorded only "make.wordpress.org." Nineteen links: the 7.1 release post, three contributor profiles, seven timeanddate.com links (one per schedule row), the Slack release-leads room (twice), Trac report, GitHub project board, the Make chat page, the bug-scrub handbook page, translate.wordpress.org stats, and the Make/Core `core` tag archive. The post gives dates, leads, and scope rules; it gives no ticket counts, no named tickets, and no description of what "volume and severity" means in numbers. The 18-section template is applied per the standing decision; several sections are one or two lines and say so. > # 🏷️ Title: WordPress 7.1.1 Release Schedule > ## 🧭 Table of Contents > - [📝 Summary](#-summary) > - [📖 Main Content](#-main-content) > - [🗒️ Notes](#️-notes) > - [📚 References](#-references) > - [🗣️ Paraphrase](#️-paraphrase) > - [📰 Newsletter](#-newsletter) > - [✅ Action Items](#-action-items) > - [🧪 Hypotheses](#-hypotheses) > - [📊 Methodology](#-methodology) > - [❓ Questions](#-questions) > - [🔮 Future Research](#-future-research) > - [💡 Implications](#-implications) > - [🧠 Learning Styles Assessment](#-learning-styles-assessment) > - [📊 Accessibility Assessment](#-accessibility-assessment) > - [🌍 DEIB Assessment](#-deib-assessment) > - [✅ Logical Validity](#-logical-validity) > - [🛡️ DARVO Analysis](#-darvo-analysis) > - [🎯 Conclusion](#-conclusion) > ### 🔗 References > - Source: https://make.wordpress.org/core/2026/09/02/wordpress-7-1-1-release-schedule/ > - Linked: WordPress 7.1 "Mary Lou" release post — https://wordpress.org/news/2026/08/mary-lou/ > - Linked: co-lead profiles — https://profiles.wordpress.org/adamsilverstein/ · https://profiles.wordpress.org/adrianduffell/ · https://profiles.wordpress.org/andraganescu/ > - Linked (×7): timeanddate.com fixed-time pages, one per schedule row (e.g. https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260917T1500) > - Linked (×2): 7.1 Release Leads Slack room — https://wordpress.slack.com/archives/C0B4Q0RJVAT (the anchor's `data-id` attribute points at a different channel, C08MVR1MU2K — see Notes) > - Linked: Trac report 4 (minor-release workflow) — https://core.trac.wordpress.org/tickets/minor/workflow > - Linked: 7.1.x editor tasks board — https://github.com/orgs/WordPress/projects/302 > - Linked: #core room — https://make.wordpress.org/chat/ > - Linked: Leading bug scrubs (handbook) — https://make.wordpress.org/core/handbook/tutorials/leading-bug-scrubs/ > - Linked: translate.wordpress.org stats — https://translate.wordpress.org/stats/ > - Linked: "#core" — https://make.wordpress.org/core/tag/core/ (a tag archive, not the chat page — see Notes) > ## 📝 Summary > **What this is.** The schedule and scope statement for WordPress 7.1.1, the first maintenance release of the 7.1 branch. Adam Silverstein posts it on Make/Core two weeks after 7.1 "Mary Lou" shipped (2026-08-19). Co-leads are @adamsilverstein, @adrianduffell, and @andraganescu. > **The schedule.** Two weeks from first scrub to release, all times UTC and all marked as estimates: > | Date/Time (UTC) | Event | > |---|---| > | Thursday, September 3, 2026, 02:00 PM | Bug Scrub | > | Friday, September 4, 2026, 02:00 PM | Bug Scrub | > | Tuesday, September 8, 2026, 08:00 PM | Bug Scrub. WordPress 7.1.2 Milestone will be opened, and some tickets may be punted. | > | Wednesday, September 9, 2026, 10:00 AM | Bug Scrub | > | Thursday, September 10, 2026, 05:30 PM | WordPress 7.1.1 RC1 | > | Tuesday, September 15, 2026, 02:00 PM | Bug Scrub. | > | Thursday, September 17, 2026, 03:00 PM | WordPress 7.1.1 General Release | > Five scrubs, one RC, one release. Seven days between RC1 and general release. The scrubs rotate across time zones: 14:00, 14:00, 20:00, 10:00, 14:00 UTC. > **The scope rule.** "Bug-fix only maintenance release." A ticket qualifies if it's a regression introduced during the 7.1 cycle or something intentionally deferred at the end of the 7.1 cycle. The tracking surfaces are Trac report 4 and the 7.1.x editor tasks board on GitHub. > **The stated reason.** "The volume and severity of tickets mean that the maintenance release should be prepared habitually." No numbers accompany "volume" or "severity." > **Bottom line.** A routine minor-release post with the standard shape — leads, scrub calendar, RC, release, scope rule, how to help. The one sentence that carries information beyond the calendar is the rationale, which says the post-7.1 ticket flow was heavy enough to justify the release without saying how heavy. > ## 📖 Main Content > **Where the tickets came from.** The post names three intake channels contributors have been watching since 7.1: the WordPress.org Support Forums, Trac, and the Gutenberg repository on GitHub. Listing Gutenberg separately matters for the scope of the release — editor bugs live in a different tracker from Core bugs, and the post gives them their own board (GitHub project 302) alongside the Trac report. > **"Prepared habitually."** The phrase is unusual. The plain reading is that minor releases after a major are routine and this one is being run as routine, prompted by ticket volume and severity. It's not a claim that anything unusual happened. The post doesn't quantify volume, name any ticket, or characterize severity beyond the word itself. > **Leads.** Three co-leads. Adam Silverstein (the byline) is a Core committer with a performance and media background; Adrian Duffell and Andrei Draganescu are both named as co-leads with profile links only. The post doesn't assign roles among the three. The `@jorbin` mention visible on the live page is in the page furniture (a mention elsewhere on the Make/Core page), not in the post body — the captured HTML has no such mention. > **The schedule's shape.** Scrub → scrub → scrub (with 7.1.2 milestone opened and punts) → scrub → RC1 → scrub → release. The milestone-opening on September 8, two days before RC1, is the point where the ticket list gets cut: anything not ready moves to 7.1.2. The post-RC scrub on September 15 is for RC regressions. All of this is standard for a WordPress minor; the post is following the template, not describing a new process. > **Times are estimates.** The post says so directly: exact times "will be announced in the 7.1 Release Leads room and will be based on availability of individuals helping with the release." The schedule table is a plan, not a commitment. > **Maintenance vs. security.** The post says "bug-fix only maintenance release." It does not mention security fixes. Anything beyond that is inference; this note doesn't make it. > **Timeline context, verified against the Releases category on wordpress.org/news.** The 7.0.x security cluster from the Repository CSI note — 7.0.2 (2026-07-17), 7.0.3 (2026-08-06), 7.0.4 (2026-08-12) — all shipped *before* 7.1 (2026-08-19). 7.1 therefore already carries those fixes, and 7.1.1 is the first release on the 7.1 branch, 29 days after the major. This corrects the lead's pre-check note, which had the order reversed. > **How to help.** Attend scrubs in #core, run your own scrubs (handbook link), do the development-testing-review work every open ticket needs, and translate: "some locales have strings in 7.1 in need of translation." Coordination is in the release-leads Slack room; code decisions are in #core. > ## 🗒️ Notes > - **Two link inconsistencies, both minor but real.** > 1. The two "7.1 Release Leads" anchors have `href="…/C0B4Q0RJV Since [WordPress 7.1 was released](https://wordpress.org/news/2026/08/mary-lou/), contributors have kept a close eye on incoming reports to the WordPress.org Support Forums, Trac, and the Gutenberg repository on GitHub. The volume and severity of tickets mean that the maintenance release should be prepared habitually. This release will be co-led by [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/), [@adrianduffell](https://profiles.wordpress.org/adrianduffell/), and [@andraganescu](https://profiles.wordpress.org/andraganescu/). #### Schedule | Date/Time | Event | | --- | --- | | [Thursday, September 3, 2026 at 02:00 PM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260903T1400) | Bug Scrub | | [Friday, September 4, 2026 at 02:00 PM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260904T1400) | Bug Scrub | | [Tuesday, September 8, 2026 at 08:00 PM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260908T2000) | Bug Scrub. WordPress 7.1.2 Milestone will be opened, and some tickets may be punted. | | [Wednesday, September 9, 2026 at 10:00 AM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260909T1000) | Bug Scrub | | [Thursday, September 10, 2026 at 05:30 PM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260910T1730) | WordPress 7.1.1 RC1 | | [Tuesday, September 15, 2026 at 02:00 PM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260915T1400) | Bug Scrub. | | [Thursday, September 17, 2026 at 03:00 PM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260917T1500) | WordPress 7.1.1 General Release | Note that the above times are estimates – exact times for scrubs, RC and General release will be announced in the [7.1 Release Leads](https://wordpress.slack.com/archives/C0B4Q0RJVAT) room and will be based on availability of individuals helping with the release. #### Targeted Fixes WordPress 7.1.1 is intended as a bug-fix only maintenance release. Tickets will be included provided they are issues introduced during the 7.1 cycle or intentionally deferred at the end of the 7.1 cycle. You can follow [trac report 4](https://core.trac.wordpress.org/tickets/minor/workflow) or the [7.1.x editor tasks board](https://github.com/orgs/WordPress/projects/302) for proposed fixes. #### Get Involved with 7.1.1 Bug Scrubs will happen in the [#core room](https://make.wordpress.org/chat/) during the times posted above. Each of the open tickets is going to require development work along with testing and review. You can also [run your own scrubs](https://make.wordpress.org/core/handbook/tutorials/leading-bug-scrubs/) to help ensure that all of the correct tickets are fixed in this release. Additionally, [some locales have strings in 7.1 in need of translation](https://translate.wordpress.org/stats/). General coordination for the release will happen in the [7.1 Release Leads](https://wordpress.slack.com/archives/C0B4Q0RJVAT) room and decisions around code for the release will be made in the [#core](https://make.wordpress.org/core/tag/core/) room., WordPress 7.1.1 Release Schedule, Adam Silverstein, 01m1htcxvnztg03fcnxtcds8pa.