# Anne McCarthy Named WordPress 7.1 Release Lead > [!question] Lingering Questions > - Will the roadmap post (due the week of the article) confirm "RTC architecture in core, full feature set out," or does the scope shift once organized testing starts? > - Does two straight releases without Mullenweg as lead actually indicate durable distributed leadership, or is it noise from just two data points? > - How will AI Connectors third-party extensibility be governed/secured once it ships — Courtney is already wary of WP AI connectors generally. > [!tip] Article Ideas > - None yet — this is a dated news item; revisit only if the RTC scoping decision or the leadership-continuity pattern develops further across 7.2+. > [!link] Cross Reference > - [[3. Resources/MOCs/Open Source Governance MOC]] — release-lead composition and sponsorship balance as a governance signal > - [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] — AI Connectors extensibility widens the plugin-ecosystem AI surface worth tracking alongside hosting/security concerns > [!quote] Vocabulary > - **RTC** — Real-Time Collaboration, the multi-user simultaneous-editing feature pulled from WordPress 7.0 pending re-evaluation > - **AI Connectors** — the WordPress core screen/API for configuring third-party AI providers, gaining extensibility in 7.1 ## Bib capsule WP Tavern (via therepository.email), "Anne McCarthy Named WordPress 7.1 Release Lead," published 2026-06-18. Source: [[3. Resources/Readwise/Full Document Contents/Articles/Anne McCarthy Named WordPress 7.1 Release Lead]]. ## Author's thesis Automattic's Anne McCarthy takes her first turn as WordPress release lead for 7.1, inheriting the project's most contentious open decision — how much of real-time collaboration belongs in core — atop an already packed feature backlog, with the release shipping August 19, 2026, the final day of WordCamp US. ## Key arguments (≤3) 1. **The appointment itself is a governance signal.** McCarthy is the only Automattic-sponsored contributor on a 10-person, ecosystem-spanning squad, and 7.1 is the second consecutive major release without Matt Mullenweg as lead (Ventura led 7.0). 2. **RTC's core-vs-plugin scoping is the release's central decision.** Pulled from 7.0 in May pending "re-evaluation"; WCEU core-committer sentiment favors landing the underlying architecture in core while keeping the full feature set out. 3. **The rest of 7.1's scope is genuinely packed**, not incidental: client-side media processing, AI Connectors third-party extensibility, an iframed post editor, a React 19 upgrade, and Unicode support in emails/usernames/slugs. ## Claim atoms ### 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." Where/why: this is the headline open decision for the cycle; McCarthy's roadmap post (expected the week of the article) was set to confirm scope. RTC was pulled from 7.0 in May pending re-evaluation. ### 7.1 release leadership is distributed beyond Mullenweg and Automattic > [!quote] ID:rw_pending > "It's the second consecutive major release without WordPress co-founder Matt Mullenweg in the release lead role" Where/why: McCarthy is the only Automattic-sponsored contributor on a 10-person squad spanning Yoast, Hostinger/Kinsta/LOOS/ServMask sponsorship, and dedicated accessibility representation (Joe Dolson) — a composition worth tracking across future cycles as either a durable pattern or a two-data-point coincidence. ## Permanent candidates - **A WordPress major release can be led without Mullenweg in the role** — factually demonstrated twice now (7.0 under Ventura, 7.1 under McCarthy). Modest, narrowly scoped claim rather than a trend assertion; promoted below with explicit n=2 hedging. - RTC's "architecture in core, feature set optional" framing as a general extensibility pattern — not promoted; too tied to this specific feature decision to generalize yet. ## Processing checklist - [ ] Watch for McCarthy's 7.1 roadmap post to confirm RTC scope - [ ] Revisit the leadership-continuity claim after WordPress 7.2's release lead is announced - [ ] Track AI Connectors extensibility for security/governance follow-up sources - [x] Connect into the relevant MOC — [[3. Resources/MOCs/Open Source Governance MOC]] ## Links - [[3. Resources/MOCs/Open Source Governance MOC]] — release-lead composition, sponsorship balance, and the RTC core-scoping decision are all governance-design questions this MOC tracks