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 > <!-- deep-read:sections start --> ## 🧭 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="…/C0B4Q0RJVAT"` but `data-id="…/C08MVR1MU2K"`. The `data-id` is the Gutenberg link block's stored URL; the `href` is what renders. A block copied from a prior release post and re-pointed would produce this shape. Readers follow the href, so no user-facing problem, but it's a tell that the post was templated from an earlier one. 2. "#core room" links to https://make.wordpress.org/chat/ (the Slack signup page) while "#core" in the last paragraph links to https://make.wordpress.org/core/tag/core/ (a tag archive on the blog). Same channel, two unrelated targets. - **No ticket numbers.** A reader who wants to know *what* is being fixed has to open Trac report 4 or the GitHub board. That's normal for schedule posts, but it means this document has no content about 7.1.1 itself — only about its calendar. - **Gutenberg 23.9 cross-reference.** The "What's New in Gutenberg 23.9" post (same day, 2026-09-02, doc `01m1hfejz90mbmyesgbdbqmt1w`) is the plugin release; the 7.1.x editor tasks board is where editor fixes destined for Core's 7.1.1 are tracked. Two different pipelines for editor changes, both live this week. - **Time zone conversions** (arithmetic from the post's UTC times; US Eastern is UTC−4 in September): Sept 3 and 4 scrubs 10:00 ET; Sept 8 scrub 16:00 ET; Sept 9 scrub 06:00 ET; RC1 Sept 10 13:30 ET; Sept 15 scrub 10:00 ET; release Sept 17 11:00 ET. - **Author.** Adam Silverstein — from the live page's `entry-author` element. Reader stored the site as author, the usual pattern for Make blog posts with no author meta tag. ## 📚 References - Silverstein, A. *WordPress 7.1.1 Release Schedule*, Make WordPress Core, 2026-09-02. - *WordPress 7.1 "Mary Lou"*, WordPress News, 2026-08-19 (linked; publish date checked on the Releases category page, body not read for this note). - WordPress News, Releases category — order of 7.0.2 (2026-07-17), 7.0.3 (2026-08-06), 7.0.4 (2026-08-12), 7.1 (2026-08-19). Checked for the timeline paragraph. - Trac report 4 — https://core.trac.wordpress.org/tickets/minor/workflow (linked; not read). - 7.1.x editor tasks board — https://github.com/orgs/WordPress/projects/302 (linked; not read). - Leading bug scrubs, Core Handbook — https://make.wordpress.org/core/handbook/tutorials/leading-bug-scrubs/ (linked; not read). - Cross-reference: this batch's Repository CSI note (7.0.x security cluster) and Gutenberg 23.9 note. ## 🗣️ Paraphrase Since 7.1 shipped, we've been watching the forums, Trac, and the Gutenberg repo, and there's enough coming in — in both count and seriousness — that we're running the usual maintenance release. Adam, Adrian, and Andrei are leading it. Here's the plan: scrubs on September 3, 4, 8, 9, and 15; RC1 on September 10; release on September 17. Times are UTC and approximate — we'll confirm each one in the release-leads Slack room depending on who's around. This is bug-fix only: 7.1 regressions and things we deliberately pushed out at the end of 7.1. Follow Trac report 4 or the GitHub editor board to see what's proposed. Come to the scrubs in #core, run your own if you want, and every ticket needs someone to write, test, and review the fix. Some locales still have 7.1 strings to translate. Coordination happens in the leads room; code decisions happen in #core. ## 📰 Newsletter **WordPress 7.1.1 is scheduled for September 17.** Adam Silverstein posted the maintenance-release schedule on Make/Core: five bug scrubs starting September 3, RC1 on September 10, general release Thursday, September 17 at 15:00 UTC. Co-leads are Adam Silverstein, Adrian Duffell, and Andrei Draganescu. The release is "bug-fix only" — 7.1-cycle regressions and deliberately deferred tickets, tracked in Trac report 4 and the 7.1.x editor board on GitHub. The 7.1.2 milestone opens September 8, when unready tickets get punted. All times are estimates confirmed in the release-leads Slack room. The stated trigger is "the volume and severity of tickets" since 7.1 shipped August 19, with no figures attached. The post also flags that some locales still have untranslated 7.1 strings. If you want in: scrubs in #core at the posted times, or run your own. ## ✅ Action Items **DevRel** - Not applicable to this source. **OSPO** - Not applicable to this source. **Community** - Not applicable to this source. **WordPress teams** (Core, Core Performance, Core AI, Core Program Team, Mobile, Playground, Community, Training, Marketing, Support, Design, Documentation, Photos, TV, Polyglots, Accessibility, Meta, CLI, Hosting, Tide, Openverse, Themes, Plugins) - **Core:** the schedule and scope rule are the whole post; the two link inconsistencies (Slack `data-id` vs `href`, "#core" → tag archive) are one-minute fixes for whoever edits the post next. `#action/h3` - **Polyglots:** the post explicitly calls out 7.1 strings still needing translation in some locales. `#action/h2` - **Support:** forum reports are named as one of the three intake channels feeding 7.1.1; the scrub dates are when those reports get triaged into tickets or not. `#action/h3` - **Hosting:** general release target is 2026-09-17 15:00 UTC, estimate. Auto-update windows follow from that. `#action/h3` - **Documentation:** release-notes work starts once the ticket list is cut on September 8. `#action/h3` - All other teams: not applicable to this source. **The WPOCC** - Not applicable to this source. **FAIR** - Not applicable to this source. **Personal (Courtney)** - **Timeline correction for the batch:** 7.0.2/7.0.3/7.0.4 all predate 7.1 (Aug 19); 7.1.1 is the first 7.1-branch release. Any note or post that says otherwise needs the order fixed. `#action/h2` - **Trac report 4 and GitHub project 302** are the two places the actual 7.1.1 ticket list lives; this post has none of it. Read those if 7.1.1 content matters for anything you're writing. `#action/h3` - The release date (Sept 17) falls in your first week at Pantheon (start Sept 14). Fact, not a scheduling recommendation. `#action/h3` ## 🧪 Hypotheses - **H-A:** The 7.1.1 ticket list will be dominated by editor (Gutenberg) regressions rather than Trac tickets, because the post gives Gutenberg its own tracking board and names the GitHub repo as an intake channel. *Testable on September 17 by counting fixes by tracker in the release post.* - **H-B:** At least one scheduled time will move, because the post says times depend on lead availability and five scrubs across four different UTC slots is hard to hold. *Testable against the release-leads room announcements.* - **H-C:** The "volume and severity" phrasing is template language carried over from prior minor-release posts, not a signal about 7.1's quality. *Testable by diffing against the 7.0.1 and 6.9.1 schedule posts.* - **H-D:** The Slack `data-id`/`href` mismatch shows the post was templated from a prior release's schedule post. *Testable by checking whether C08MVR1MU2K is the 7.0 release-leads channel.* ### 📊 Methodology A schedule announcement, not an argument. It states a plan (dates, leads, scope) and a one-sentence rationale. Nothing is offered in evidence for the rationale, and none is expected in this genre. The right way to use it is as a calendar and as a pointer to the two ticket lists; the right way to evaluate the rationale is to open Trac report 4 and count. ### ❓ Questions - How many 7.1 regressions are open on Trac report 4 and the GitHub board as of September 2? What severities? - Does "prepared habitually" mean this is the first of a cadence (7.1.2 already has a milestone), or just that minors are routine? - Is the Slack `data-id` C08MVR1MU2K the 7.0 release-leads channel? (If yes, H-D holds.) - Why does "#core" link to a tag archive in the last paragraph while "#core room" links to the chat signup page? - Which locales have untranslated 7.1 strings, and how many? - Will 7.1.1 carry any security fixes? The post says bug-fix only and nothing else. ### 🔮 Future Research - On or after September 17, read the 7.1.1 release post and compare the shipped fix list against the September 8 cut. - Diff this post against the 7.0.1 schedule post to test H-C (template language). - Pair with the Gutenberg 23.9 note: which editor fixes went through the plugin, which through Core's 7.1.x board. ### 💡 Implications **For contributors.** Five scrub windows across four UTC slots — 10:00, 14:00, 17:30 (RC), 20:00 — so at least one lands in daytime for most regions. The handbook link means anyone can run an off-schedule scrub. **For the project.** The 7.1.2 milestone opening on September 8, before 7.1.1 RC1, is the project's standing pattern: the next minor exists before the current one is cut. That's how punting stays cheap. **For hosts and site owners.** September 17 at 15:00 UTC is the estimate; auto-updates for minors follow within hours. Nothing in the post suggests anything urgent about the update. **For the batch.** This post fixes a date: 7.1 shipped August 19, after all three 7.0.x security releases. The Repository CSI note's cluster and this release are sequential, not overlapping. ## 🧠 Learning Styles Assessment **Read/write** — served. Short prose plus a table. **Visual** — the table is the one visual structure, and it's the right one for a schedule. **Kinesthetic** — served indirectly: every date links to a timeanddate.com converter, and the handbook link tells you how to run a scrub yourself. **Auditory** — not served. **Global vs. sequential** — sequential by design; the table is chronological. **Overall:** a well-shaped schedule post. The timeanddate links are the small courtesy that makes a UTC table usable worldwide. ## 📊 Accessibility Assessment Assessment of the captured HTML only. Not a WCAG audit of make.wordpress.org. #### Alternative text and non-text content No images in the captured content. #### Keyboard navigation Not testable from the capture. Standard Make blog theme; no interactive elements in the post body beyond links. #### Contrast and readability Not assessable from HTML. Prose is short and plain. #### Text resizing and reflow A two-column table with long date strings in column one. At narrow widths the theme's table handling determines whether it reflows or scrolls; not testable from the capture. #### Media and captions No media. #### Forms and interactions None in the post body. #### Standards reference WCAG 2.2 AA is the standard the assessment above is loosely mapped to (1.1.1, 2.4.1, 1.4.3, 1.4.10, 1.2, 1.3.1). The table has a header row (`<th>Date/Time</th><th>Event</th>`), which satisfies the basic 1.3.1 expectation. One 2.4.4 Link Purpose note: "#core" and "#core room" have near-identical anchor text but point at unrelated pages. ## 🌍 DEIB Assessment #### Cultural breadth UTC throughout with a timeanddate.com converter link on every row — the correct choice for a global contributor base. Scrub times span 10:00–20:00 UTC, which covers European and American daytime and Asia-Pacific evening/morning edges. #### Inclusive language Neutral. "Contributors," "individuals helping with the release," "you." #### Neurodiversity support Chronological table, one rule per sentence, clear headings (Schedule / Targeted Fixes / Get Involved). The "times are estimates" caveat is stated once, plainly. #### Representation Three named leads with profile links. No other contributors named; the post is about process, not people. #### Psychological safety "Run your own scrubs" with a handbook link lowers the barrier to participation. The post names where coordination and decisions happen, which tells a newcomer where to show up. ## ✅ Logical Validity **Argument structure.** Premise: ticket volume and severity since 7.1 are high enough to warrant a maintenance release. Conclusion: schedule one. Valid form; the premise is asserted, not shown. In this genre that's normal — the evidence is the ticket list the post links to, not the post. **Hedges.** "Estimates," "will be based on availability," "may be punted." The post is honest that the calendar is provisional. **Gaps.** No ticket counts. No definition of "severity." "Prepared habitually" is unclear on whether it means "as routine" or "regularly from now on." **Fallacies.** None. **Verdict.** Sound as a schedule; empty as an argument, and not trying to be one. ## 🛡️ DARVO Analysis Not applicable to this source. No accusation, no reversal, no victim/offender framing. A schedule post with a one-sentence rationale. ## 🎯 Conclusion WordPress 7.1.1 is a bug-fix-only maintenance release led by Adam Silverstein, Adrian Duffell, and Andrei Draganescu, with five scrubs from September 3, RC1 on September 10, and general release targeted for Thursday, September 17, 2026 at 15:00 UTC — all times estimates to be confirmed in the release-leads Slack room. Scope is 7.1-cycle regressions plus deliberately deferred tickets, tracked in Trac report 4 and GitHub project 302; the 7.1.2 milestone opens September 8. The post's only claim beyond the calendar is that ticket "volume and severity" justify the release, and it attaches no numbers. For Courtney the useful outputs are a fixed date, a timeline correction — 7.1 (Aug 19) shipped after 7.0.2/7.0.3/7.0.4, so 7.1.1 is the first release on the 7.1 branch — and a pointer to the two ticket lists where the release's actual content lives. ## 🔄 Refactor Appendix — WordPress 7.1.1 Release Schedule ### 📚 Literature Atoms (H3) #### [H1] The rationale: volume and severity, unquantified > [!quote] ID:rw_01m1htcxvnztg03fcnxtcds8pa > "Since WordPress 7.1 was released, 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." Three intake channels named; no counts. The one sentence in the post that isn't calendar. Tags: `#atom/literature/h1` #### [H2] Scope rule: 7.1 regressions and deliberate deferrals only > [!quote] ID:rw_01m1htcxvnztg03fcnxtcds8pa > "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 or the 7.1.x editor tasks board for proposed fixes." The eligibility test for a 7.1.1 ticket, and the two places the list lives. Tags: `#atom/literature/h2` #### [H3] The schedule is an estimate contingent on lead availability > [!quote] ID:rw_01m1htcxvnztg03fcnxtcds8pa > "Note that the above times are estimates – exact times for scrubs, RC and General release will be announced in the 7.1 Release Leads room and will be based on availability of individuals helping with the release." Read the table as a plan. Confirmation happens in Slack. Tags: `#atom/literature/h3` ### 🧠 Permanent Candidates (H4) #### [P1] A release schedule post is a calendar plus a pointer, not a changelog Minor-release schedule posts on Make/Core carry dates, leads, a scope rule, and links to the ticket lists. They don't carry the tickets. Anyone analyzing "what's in 7.x.y" from the schedule post alone has nothing; the content is in Trac and GitHub. *Candidate; one source, but the pattern is consistent across WordPress minor-release posts and generalizes to any project with a separate tracker.* Links: [[WordPress Release Process]] · [[WordPress Release Audit Method]] · [[WordPress Core MOC]] Tags: `#atom/zettel/z1` ### ✏️ Fleeting Queue - 7.1 shipped 2026-08-19, after 7.0.2 (Jul 17), 7.0.3 (Aug 6), 7.0.4 (Aug 12). Lead's pre-check had this reversed; corrected here. `#atom/fleeting/f1` - Slack anchor `data-id` (C08MVR1MU2K) ≠ `href` (C0B4Q0RJVAT) — templated post tell. `#atom/fleeting/f1` - "#core" → tag archive vs "#core room" → chat signup page. `#atom/fleeting/f1` - "Prepared habitually" — odd phrasing; probably "as routine." `#atom/fleeting/f1` ### → Things 3 (max 2 actions) 1. **On or after 2026-09-17, read the 7.1.1 release post** and compare the shipped fix list against Trac report 4 / GitHub project 302 as of the September 8 cut. `#action/h3` 2. **Fix the 7.0.x/7.1 ordering** anywhere in this batch's notes or drafts that states 7.1 shipped before the security cluster. `#action/h2` <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/WordPress 7.1.1 Release Schedule.md|WordPress 7.1.1 Release Schedule by Adam Silverstein]] ## Highlights - 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. ([View Highlight](https://read.readwise.io/read/01m1http34jnbppx2w80k98enw)) - Note: H1 — The rationale: three intake channels named, "volume and severity" unquantified. The one sentence in the post that isn't calendar. #atom/literature/h1 - Tags: atom/literature/h1 - 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. ([View Highlight](https://read.readwise.io/read/01m1htvfwcta4yzbfbjmsqe4ka)) - Note: H3 — The schedule is an estimate contingent on lead availability; confirmation happens in Slack. Note the anchor's data-id (C08MVR1MU2K) differs from its href (C0B4Q0RJVAT) — templated-post tell. #atom/literature/h3 - Tags: atom/literature/h3 - 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. ([View Highlight](https://read.readwise.io/read/01m1htv34bygkjp6mvqft7pefw)) - Note: H2 — Scope rule: 7.1-cycle regressions and deliberate deferrals only; the ticket list lives in Trac report 4 and GitHub project 302, not in this post. #atom/literature/h2 - Tags: atom/literature/h2