Anne McCarthy Named WordPress 7.1 Release Lead  🔗 **Source:** [Anne McCarthy Named WordPress 7.1 Release Lead](https://www.therepository.email/anne-mccarthy-named-wordpress-7-1-release-lead) > [!note]+ Document Notes > tags: [wordpress, wordpress-7-1, release-leadership, real-time-collaboration, gutenberg, ai-connectors] > author: [MISSING] > source: The Repository > reference: https://www.therepository.email/anne-mccarthy-named-wordpress-7-1-release-lead > date created: 2026-06-18 11:30 > > # 🏷️ Title: Anne McCarthy Named WordPress 7.1 Release Lead > <!-- 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 - [Make WordPress Core — 7.1 release squad announcement](https://make.wordpress.org/core/) - [WordPress 7.0 RC3 (RTC pulled)](https://make.wordpress.org/core/) ## 📝 Summary - **What happened.** Automattic's Anne McCarthy was named release lead for WordPress 7.1 — their first time in the role — announced by Fueled-sponsored contributor Jeffrey Paul on the Make WordPress Core blog. It's the second consecutive major release without Matt Mullenweg as lead (Matías Ventura led 7.0). - **Why it matters.** 7.1 inherits the decision on **real-time collaboration (RTC)**, pulled from 7.0 in May and slated for "re-evaluation." A WCEU core-committer meeting voiced a "strong opinion, loosely held" that the *full RTC feature set* should stay out of core but the *underlying architecture* should land — a consequential scoping call McCarthy's forthcoming roadmap must resolve. - **Key stakeholders.** McCarthy (Automattic's only sponsored contributor on the 10-person squad), the squad (coordination, technical, triage, test leads from across the ecosystem — Yoast, Hostinger/Kinsta-sponsored, accessibility), and the WordPress community testing RTC via the Gutenberg plugin. - **Risks and tradeoffs.** A first-time lead inheriting a contentious, deferred feature; a packed scope (client-side media processing, AI Connectors extensibility, iframed editor, React 19, Unicode). Leadership continuity questions persist (two releases without Mullenweg). - **Bottom line.** 7.1 ships **August 19** (final day of WordCamp US 2026, Phoenix); the roadmap post (expected this week) will confirm scope, with RTC's architecture-vs-feature-set question the headline decision. ## 📖 Main Content - **The appointment.** Anne McCarthy (Automattic's Architecture and Open Source Director) leads 7.1 — first time; the only Automattic-sponsored contributor on a 10-person squad. Second straight release without Mullenweg as lead. - **The squad.** Release coordination: Benjamin Zekavica (Morvance) + Krupa Nanda (freelance QA). Technical leads: Aki Hamano (freelance, sponsored by LOOS/Hostinger/Kinsta/ServMask) + Joe Dolson (Accessibility Team, Accessible Web Design). Triage: Adrian Duffell, Sajjad Hossain Sagor, Sergey Biryukov (Yoast). Test leads: Huzaifa Al Mesbah (Buzz Geek), Nikunj Hatkar (TeamUpdraft). Cross-ecosystem composition, with explicit accessibility representation. - **McCarthy's track record.** Long-time, well-respected contributor already deep in the 7.1 cycle; launched a collaborative-editing outreach effort modeled on the Full Site Editing Outreach Program they ran during block-editor development — recruiting early adopters to test RTC via the Gutenberg plugin. Drafting a 7.1 roadmap post (expected this week). - **The RTC decision.** RTC was pulled from 7.0 in May (RC3 said it'd be "re-evaluated" in 7.1). At a WCEU core-committer meeting, attendees held a "strong opinion, loosely held" that the *full feature set* shouldn't be in core but the *underlying architecture* should — the central scoping question for 7.1. - **The rest of the scope.** Deferred/in-progress: client-side media processing (punted from 7.0, expected to ship after a recent call for testing), third-party provider extensibility + other AI Connectors screen updates, an iframed post editor, a React 19 upgrade, and Unicode support in emails/usernames/slugs. - **Timing.** 7.1 scheduled for **August 19, 2026**, coinciding with the final day of WordCamp US 2026 in Phoenix. ### 🗒️ Notes - McCarthy = first-time release lead; Automattic Architecture & Open Source Director; only Automattic-sponsored contributor on the squad. - **Second consecutive release without Mullenweg** as lead (Ventura led 7.0) — a continuity/governance signal. - **RTC** is the headline decision: pulled from 7.0; WCEU consensus leaning "architecture in core, full feature set out." - Packed 7.1 scope: client-side media processing, **AI Connectors** extensibility (note: Courtney is wary of WP AI connectors), iframed editor, React 19, Unicode in emails/usernames/slugs. - Squad spans the ecosystem (Yoast, Hostinger/Kinsta/LOOS/ServMask sponsorship, accessibility) — only one Automattic sponsor. - Ship date **Aug 19, 2026** = last day of WCUS 2026 (Phoenix). - Roadmap post expected this week (confirms full scope). - Disclosure: Automattic-owned Pressable sponsors The Repository. ## 📚 References - Make WordPress Core blog — 7.1 release squad post (Jeffrey Paul) - WordPress 7.0 RC3 announcement (RTC pulled, "re-evaluated") - WordCamp Europe 2026 core-committer meeting (RTC architecture-vs-feature-set) - Full Site Editing Outreach Program (McCarthy's model for the RTC outreach) - WordCamp US 2026 (Phoenix), Aug 2026 ## 🗣️ Paraphrase - Anne McCarthy is the new WordPress 7.1 release lead, her first time, and the second straight release not led by Mullenweg. - She heads a 10-person, ecosystem-spanning squad and is already running RTC early-adopter outreach via the Gutenberg plugin. - The biggest open question is whether RTC's full feature set or just its architecture lands in core. - 7.1 also carries client-side media processing, AI Connectors extensibility, an iframed editor, React 19, and Unicode support. - It ships August 19, the final day of WordCamp US 2026, with a scope-confirming roadmap due this week. ## 📰 Newsletter **Anne McCarthy takes the WordPress 7.1 wheel — and the RTC decision with it** WordPress 7.1 has a release lead: Automattic's Anne McCarthy, stepping in for the first time and inheriting the thorniest open question in core — what to do with real-time collaboration. RTC was pulled from 7.0 back in May; the WordCamp Europe core-committer read is "strong opinion, loosely held" that the *architecture* belongs in core but the *full feature set* doesn't. McCarthy's already running RTC early-adopter outreach (modeled on her Full Site Editing Outreach Program), and a roadmap post is due this week. Two things worth flagging for the WordPress crowd: it's the second straight release without Mullenweg as lead (a governance signal worth watching), and the 7.1 scope is stacked — client-side media processing, **AI Connectors extensibility**, an iframed editor, React 19, and Unicode in emails/usernames/slugs. Mark the date: 7.1 ships August 19, the last day of WordCamp US in Phoenix. ## ✅ Action Items #### DevRel - Developer advocacy: brief the community on the 7.1 scope + RTC decision once the roadmap drops. - Education: prep testing guidance for client-side media processing + RTC early-adopter program. - Developer experience: track the iframed editor + React 19 upgrade for breaking-change docs. - Developer marketing: WCUS 2026 (Aug 19) release-day content. - Community management: amplify McCarthy's RTC outreach call for testers. - Internal/external/cross-project: monitor AI Connectors extensibility for downstream plugin impact. #### OSPO - Strategic Alignment: note the leadership-continuity signal (2 releases without Mullenweg) for governance tracking. - Other functions: Not applicable to this source. #### Community - Contributors: volunteer for RTC testing / triage; the squad models cross-ecosystem participation. - Ecosystem: Not applicable beyond participation. #### WordPress - Core: the 7.1 cycle — RTC architecture-vs-feature-set is the key call. - Core Performance: client-side media processing is a perf-relevant feature shipping in 7.1. - Core AI: **AI Connectors** third-party provider extensibility is in scope — track closely. - **Core Program Team:** the release squad + roadmap cadence is the coordination artifact. - Mobile / Playground: test 7.1 betas in Playground. - Community: WCUS 2026 release-day programming. - Training: update learning paths for React 19 / iframed editor changes. - Marketing: release narrative around RTC + AI Connectors. - Support: prep for RTC/AI-connector support questions. - Design: iframed editor + admin UX implications. - Documentation: dev-notes for React 19, Unicode, iframed editor, AI Connectors. - Accessibility: Joe Dolson on the squad — track a11y of RTC + iframed editor. - Polyglots: **Unicode in usernames/slugs/emails** has i18n implications — review. - Meta: .org infra for Unicode usernames/slugs. - CLI / Hosting / Tide / Themes / Plugins: AI Connectors extensibility + React 19 may affect plugins/themes — Tide checks. #### The WPCC - Programs/Projects: contributor pathways via the release squad model. - Funding experiments: Not applicable to this source. ### FAIR - Technical independence: RTC "architecture in core, feature set optional" is itself a federation/extensibility stance worth noting. - Policies and covenants: leadership-continuity and sponsorship balance (one Automattic sponsor on the squad) are governance signals. ## 🧪 Hypotheses - H1: 7.1 will land RTC's underlying architecture but not the full feature set (per the WCEU consensus). - H2: A release led by a non-Mullenweg, non-solely-Automattic squad signals durable distributed release leadership. - H3: Client-side media processing ships in 7.1 (it cleared a call for testing). - H4: AI Connectors third-party extensibility will expand the plugin ecosystem's AI surface (and the associated security/governance questions). ### 📊 Methodology - H1/H3: track the roadmap post + beta/RC notes against shipped scope. - H2: longitudinal analysis of release-lead composition and sponsorship over several cycles. - H4: monitor plugin adoption of AI Connectors extensibility post-7.1. ### ❓ Questions - Will the roadmap confirm RTC architecture-only, or attempt the full feature set? - What does "second release without Mullenweg as lead" mean for project governance long-term? - How will AI Connectors extensibility be secured/governed (given prior community wariness)? - Does the Aug 19 / WCUS coincidence pressure the timeline? ### 🔮 Future Research - The evolving WordPress release-leadership model and its governance implications. - RTC architecture's downstream effect on collaborative-editing plugins. - AI Connectors extensibility security posture. ### 💡 Implications - **Practice:** plan for React 19, iframed editor, and Unicode changes; test RTC early. - **Policy/governance:** distributed release leadership + sponsorship balance are watch signals. - **Security:** AI Connectors extensibility widens the AI attack/governance surface. - **Education:** prep contributors/users for the 7.1 feature shifts. ### 🧠 Learning Styles Assessment - Reading level estimate: concise tech-news; ~Flesch–Kincaid Grade 11–12. Flesch Reading Ease ~45. #### 👀 Visual learners - Present: a feature image (WCEU 2023); no diagrams. - Improve: a squad org-chart and a 7.1 scope/timeline graphic. #### 🔊 Aural learners - Present: none. Improve: a short audio brief. #### 🗣️ Verbal learners - Present: clear names/roles; defined acronyms (RTC). Improve: glossary (RTC, iframed editor, AI Connectors). #### 🧩 Kinesthetic learners - Present: implicit call to test RTC. Improve: a "how to test 7.1 features" checklist. #### 🧠 Logical learners - Present: structured roster + scope list. Improve: a deferred-vs-shipping table. #### 🧑‍🤝‍🧑 Social learners - Present: it's about a collaborative squad + outreach. Improve: links to the Slack channel / Make post. #### 🧘‍♀️ Solitary learners - Present: scannable news. Improve: N/A — "Not applicable to this source." #### 🌿 Naturalistic learners - Present: none. Improve: N/A — "Not applicable to this source." ### 📊 Accessibility Assessment #### Screen reader semantics - Present: news article with a lead image (described in alt-like opening line). - Improve: ensure proper heading structure; meaningful image alt. #### Keyboard navigation - Present: standard article. Improve: verify link focus. #### Contrast and readability - Present: assume compliant. Improve: verify link contrast. #### Text resizing and reflow - Present: responsive. Improve: confirm at 200%. #### Media and captions - Present: a feature image with caption ("WordCamp Europe 2023"). Improve: descriptive alt text. #### Forms and interactions - Present: likely newsletter signup. Improve: labeled fields. #### Standards reference - WCAG 2.2 AA: 1.1.1 (image alt), 1.3.1 (headings), 1.4.3 (contrast). Note: the 7.1 feature itself (iframed editor) has its own a11y stakes — Joe Dolson is on the squad. ### 🌍 DEIB Assessment #### Cultural breadth - Present: an internationally diverse squad (names span multiple regions). - Improve: note global-contributor representation explicitly. #### Inclusive language - Present: uses "they" for McCarthy; neutral, professional. - Improve: define jargon for non-core readers. #### Neurodiversity support - Present: short, scannable. Improve: a TL;DR box. #### Representation - Present: names varied contributors and sponsors across the ecosystem; explicit accessibility role. - Improve: more on underrepresented-contributor pathways. #### Psychological safety - Present: neutral, non-partisan reporting (with a sponsorship disclosure). - Improve: N/A — "Not applicable to this source." ### ✅ Logical Validity #### Strong reasoning - Reportorial/factual: sourced to the Make Core post and named meetings; claims are attributed and verifiable. - Appropriately hedged: the RTC consensus is quoted as "strong opinion, loosely held," not stated as decided. - Transparent: discloses the Pressable/Automattic sponsorship conflict. #### Fallacies - **None substantive** — this is straight news reporting. Minor: the framing "second consecutive release without Mullenweg" implies a governance narrative the facts only partly support (could be read as leading). Fix: present as an observation, which it largely does. #### Tone of voice - Neutral, informative, insider-aware WordPress trade reporting; light governance framing. ### 🛡️ DARVO Analysis - Deny / Attack / Reverse victim-offender: Not applicable to this source. Straight news; no accused party, no defensive posture. ## 🎯 Conclusion - **Bottom line.** Anne McCarthy leads WordPress 7.1 (first time; second straight non-Mullenweg release), inheriting the RTC scoping decision (likely architecture-in-core, full-feature-set-out per WCEU) plus a packed backlog (client-side media processing, AI Connectors extensibility, iframed editor, React 19, Unicode). Ships Aug 19, last day of WCUS 2026. - **Next steps for readers.** (1) Watch for McCarthy's 7.1 roadmap post this week. (2) Join RTC early-adopter testing via the Gutenberg plugin. (3) Track AI Connectors extensibility for security/governance. (4) Prep for React 19 / iframed editor / Unicode changes. ## 🔄 Refactor Appendix — Anne McCarthy Named WordPress 7.1 Release Lead > Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4). > Short news item — 2 atoms, 0 Permanent (news, not a durable claim). Resonance filter on. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Atoms (H3) #### [H1] WordPress 7.1 must resolve the RTC architecture-vs-feature-set question > [!quote] ID:rw_pending > "a “strong opinion, loosely held” that the full RTC feature set should not be in core, but the underlying architecture should be." **Context & use**: - RTC pulled from 7.0; re-evaluated in 7.1 — the cycle's headline decision. - McCarthy's roadmap post (this week) confirms scope. **Tags**: #xref #addendum **Highlight**: [view highlight](readwise://pending) <!-- atomicity: 1 idea ✓ --> #### [H2] 7.1 release leadership is distributed beyond Mullenweg/Automattic > [!quote] ID:rw_pending > "It’s the second consecutive major release without WordPress co-founder Matt Mullenweg in the release lead role" **Context & use**: - McCarthy is the only Automattic-sponsored contributor on a 10-person, ecosystem-spanning squad. - A governance/continuity signal worth tracking across cycles. **Tags**: #xref #share **Highlight**: [view highlight](readwise://pending) <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### [P1] None worth promoting This is a dated news item, not a durable claim. The governance-continuity observation (H2) is worth watching across releases but isn't yet a standalone Permanent claim — revisit if the pattern holds over 7.2+. ### ✏️ Fleeting Queue - [F1] Watch for McCarthy's WP 7.1 roadmap post (this week) to confirm RTC + AI Connectors scope — https://www.therepository.email/anne-mccarthy-named-wordpress-7-1-release-lead #fleeting #inbox - [F2] Track AI Connectors third-party extensibility for security/governance (Courtney is wary of WP AI connectors). #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Add WP 7.1 (ship Aug 19, WCUS) + RTC decision to the WordPress tracking notes — #things - [ ] Join / share the RTC early-adopter testing call via the Gutenberg plugin — #things <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/Anne McCarthy Named WordPress 7.1 Release Lead.md|Anne McCarthy Named WordPress 7.1 Release Lead by therepository.email]] ## Highlights - Fueled-sponsored core contributor Jeffrey Paul [announced the release squad](https://make.wordpress.org/core/2026/06/17/announcing-the-wordpress-7-1-release-squad/) on the Make WordPress Core blog yesterday, following a call for volunteers last month. It’s the second consecutive major release without WordPress co-founder Matt Mullenweg in the release lead role, after Gutenberg lead architect Matías Ventura [led 7.0](https://www.therepository.email/matias-ventura-named-wordpress-7-0-release-lead-as-contributors-close-in-on-real-time-collaboration-approach). ([View Highlight](https://read.readwise.io/read/01kvdgsjfe4gt0xwte4315p10y)) - Note: H2 — second consecutive release without Mullenweg as lead; McCarthy is the only Automattic-sponsored contributor on a 10-person squad — a governance/continuity signal to track. - Tags: atom/literature/h2, release-leadership - That roadmap will need to address some big open questions. Real-time collaboration was [pulled from WordPress 7.0](https://www.therepository.email/matt-mullenweg-pulls-real-time-collaboration-from-wordpress-7-0-blames-wp-engine-litigation) in May, with the RC3 announcement saying the feature would be “re-evaluated” during the 7.1 cycle. But at a core committer meeting at WordCamp Europe earlier this month, attendees expressed a “strong opinion, loosely held” that the full RTC feature set should not be in core, but the underlying architecture should be. ([View Highlight](https://read.readwise.io/read/01kvdgsfc6y7ynp1mkh6pfv9s4)) - Note: H1 — 7.1's headline decision: RTC architecture-in-core vs full-feature-set-out (WCEU "strong opinion, loosely held"). McCarthy's roadmap (this week) confirms scope. - Tags: atom/literature/h1, wordpress-7-1, real-time-collaboration