Announcing the WordPress 7.1 Release Squad ![rw-book-cover](https://s.w.org/images/home/wordpress-default-ogimage.png) 🔗 **Source:** [Announcing the WordPress 7.1 Release Squad](https://make.wordpress.org/core/2026/06/17/announcing-the-wordpress-7-1-release-squad/) > [!note]+ Document Notes > tags: [wordpress-core, release-management, open-source-governance, contributor-community, release-squad, project-coordination] > author: Make WordPress Core > source: Make WordPress Core > reference: https://make.wordpress.org/core/2026/06/17/announcing-the-wordpress-7-1-release-squad/ > date created: 2026-06-22 00:00 > > # 🏷️ Title: Announcing the WordPress 7.1 Release Squad > <!-- 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 - [WordPress 7.1 development page](https://make.wordpress.org/core/7-1/) - [WordPress 7.1 call for volunteers](https://make.wordpress.org/core/2026/05/21/wordpress-7-1-call-for-volunteers/) - [Make Team Reps](https://make.wordpress.org/updates/team-reps/) ## 📝 Summary - What happened: The WordPress 7.1 release squad has been assembled following a call for volunteers, with Anne McCarthy as Release Lead. - Why it matters: The squad sets the leadership and coordination structure that will steer the 7.1 development cycle. - Key stakeholders: The named squad members, Make Team Reps, and the broader contributor community. - Risks and tradeoffs: A smaller squad reduces overhead but leans on Make Team Reps to keep each team represented; many volunteers could not be placed. - Bottom line: 7.1 continues the lean, focused squad model used since 6.7, distributing more coordination to team reps. ## 📖 Main Content - The post announces the formation of the WordPress 7.1 release squad after the May 21, 2026 call for volunteers. Anne McCarthy leads as Release Lead. - Full roster: Release Coordination (Benjamin Zekavica, Krupa Nanda); Tech Leads (Aki Hamano, Joe Dolson); Triage Leads (Adrian Duffell, Sajjad Hossain Sagor, Sergey Biryukov); Test Leads (Huzaifa Al Mesbah, Nikunj Hatkar). - The structure mirrors the 6.7, 6.8, 6.9, and 7.0 cycles: a smaller, focused squad that pushes more coordination onto Make Team Reps so each team's priorities stay represented while overhead drops. A stated secondary goal is reducing overlap between a Make Team Rep and that team's Release Squad Leads. - "Release Squad" — the rotating leadership group responsible for shepherding a WordPress version through its release cycle. "Make Team Reps" — designated representatives of each contributor team (Core, Design, Docs, Polyglots, and others). - The post notes volunteers far outnumbered roles; selection favored experience and focus aligned with 7.1's needs. Unselected volunteers are pointed to testing, bug scrubs, triage, and documentation. Noteworthy Contributors will be captured from Team Reps near the cycle's end. - No contested claims; this is a procedural announcement, not an argument. ### 🗒️ Notes - Release Lead: Anne McCarthy (@annezazu). - Release Coordination: Benjamin Zekavica, Krupa Nanda. - Tech Leads: Aki Hamano, Joe Dolson. - Triage Leads: Adrian Duffell, Sajjad Hossain Sagor, Sergey Biryukov. - Test Leads: Huzaifa Al Mesbah, Nikunj Hatkar. - Continuity: same lean-squad approach as 6.7 → 7.0. - Coordination model shifts representation duty toward Make Team Reps. - Generator metadata shows the site running WordPress 7.1-alpha-62517 at publish time. - Props for review: @tyxla, @annezazu, @jorbin; squad assembly help: @jorbin, @desrosj, @annezazu, @tyxla, @4thhubbard. - Tags on the post: #7-1, #planning. ## 📚 References - [WordPress 7.1 release page](https://make.wordpress.org/core/7-1/) - [WordPress 7.1 call for volunteers](https://make.wordpress.org/core/2026/05/21/wordpress-7-1-call-for-volunteers/) - [Make Team Reps](https://make.wordpress.org/updates/team-reps/) - [WordPress 6.7 call for volunteers](https://make.wordpress.org/core/2024/07/05/wordpress-6-7-planning-proposal-call-for-volunteers/) - [WordPress 6.8 call for volunteers](https://make.wordpress.org/core/2024/11/21/wordpress-6-8-call-for-volunteers/) - [WordPress 6.9 call for volunteers](https://make.wordpress.org/core/2025/07/11/wordpress-6-9-planning-proposal-and-call-for-volunteers/) - [WordPress 7.0 call for volunteers](https://make.wordpress.org/core/2026/01/09/wordpress-7-0-call-for-volunteers/) ## 🗣️ Paraphrase - The 7.1 release squad is now in place, with Anne McCarthy leading and named contributors covering coordination, tech, triage, and testing roles. - Like recent cycles, the squad stays small on purpose and relies on Make Team Reps to represent each team's priorities, cutting overhead and role overlap. More volunteers applied than there were seats, so the team thanks everyone and lists other ways to contribute. ## 📰 Newsletter - The WordPress 7.1 release squad just landed, and it's a strong lineup. Anne McCarthy takes the Release Lead chair, backed by coordination, tech, triage, and test leads pulled from across the contributor community. - The cycle keeps the lean-squad model from 6.7 through 7.0: fewer dedicated squad seats, more reliance on Make Team Reps to carry each team's priorities. Didn't make the squad this round? Testing, bug scrubs, triage, and docs all still need you. - Track the work on the [7.1 release page](https://make.wordpress.org/core/7-1/) and jump into #core on Slack, Wednesdays at 15:00 UTC. ## ✅ Action Items #### DevRel - Developer advocacy: amplify the 7.1 squad announcement and surface the call for ongoing contribution paths. - Education: point new contributors to bug scrubs and triage as low-barrier entry to a release cycle. - Developer experience: ensure 7.1 dev notes and handbook links stay current as the cycle progresses. - Developer marketing: track engagement on the announcement across Mastodon, Bluesky, and other shared channels. - Community management: welcome named squad members publicly and route unselected volunteers to active tasks. - Internal/external/cross-project: align DevRel content calendar with the 7.1 release schedule. #### OSPO - Policy & Governance: note the squad-rep coordination model as a governance pattern worth documenting. - License Compliance: not applicable to this source — an announcement post raises no licensing actions. - Security Management: not applicable to this source — no security content present. - Software Inventory: not applicable to this source — no SBOM or inventory implications. - Developer Support: flag the call-for-volunteers cadence for orgs planning contribution time. - Community Engagement: encourage sponsored contributors to engage via Make Team Reps this cycle. - Strategic Alignment: map internal roadmaps to the 7.1 timeline once milestones publish. #### Community - Maintainers: review how the lean-squad/rep model affects release hygiene this cycle. - Contributors: use bug scrubs, triage, and docs as on-ramps if not on the squad. - Sponsors: align sponsored hours with 7.1 testing and triage needs. - Ecosystem: watch for cross-team coordination handoffs between squad leads and Make Team Reps. #### WordPress - Core: track 7.1 priorities and release criteria as they emerge from the squad. - Core Performance: not applicable to this source — no performance scope announced yet. - Core AI: not applicable to this source — no AI scope in this post. - **Core Program Team:** observe how rep-driven coordination rituals work in practice for 7.1. - Mobile: not applicable to this source — no mobile content. - Playground: prepare reproducible test environments for 7.1 alpha builds. - Community: surface contribution paths in meetups during the 7.1 cycle. - Training: build learning paths around joining a release cycle mid-stream. - Marketing: schedule narrative beats around 7.1 milestones. - Support: anticipate knowledge-base updates as 7.1 features land. - Design: coordinate design representation through the Make Team Rep channel. - Documentation: keep DevHub/HelpHub 7.1 references synced with dev notes. - Photos: not applicable to this source — no Photos relevance. - TV: not applicable to this source — no WordPress.tv relevance. - Polyglots: plan translation coverage aligned to the 7.1 schedule. - Accessibility: note Joe Dolson (accessibility-focused contributor) as a Tech Lead; track a11y coverage. - Meta: ensure .org tooling supports 7.1 release workflows. - CLI: confirm WP-CLI smoke tests cover 7.1 alpha changes. - Hosting: prepare host-side compatibility checks for 7.1. - Tide: monitor plugin/theme scoring against 7.1 builds. - Openverse: not applicable to this source — no Openverse relevance. - Themes: queue theme test matrices for 7.1. - Plugins: queue plugin compatibility checks for 7.1. #### The WPCC - Programs: not applicable to this source — no WPCC program tie-in stated. - Projects: not applicable to this source — no WPCC project tie-in stated. - Funding experiments: not applicable to this source — no funding content. ### FAIR - Technical independence: not applicable to this source — no FAIR/federation scope in this post. - Policies and covenants: not applicable to this source — no governance covenant content. - Productized governance artifacts: the squad roster itself is a lightweight governance artifact worth noting. ## 🧪 Hypotheses - The lean-squad model reduces per-cycle coordination overhead relative to larger squads used before 6.7. - Shifting representation to Make Team Reps increases each team's perceived priority coverage during the cycle. - Reducing rep/squad-lead overlap lowers duplicated coordination work. - A high volunteer-to-role ratio signals contributor demand exceeding available leadership seats. - Pointing unselected volunteers to triage/testing retains contributor engagement across the cycle. ### 📊 Methodology - Compare cycle-time and contributor-count metrics across 6.7–7.1 to test overhead claims. - Survey Make Team Reps on representation workload before and after the model shift. - Track volunteer-to-role ratios across recent calls for volunteers. - Measure retention of unselected volunteers via subsequent contribution logs. ### ❓ Questions - How are squad members selected when volunteers far exceed roles, and is the rubric documented? - What specific feature focus areas will 7.1 prioritize? - How is "Noteworthy Contributors" captured from Team Reps operationalized? - Does the rep-coordination model measurably reduce overhead, or just relocate it? ### 🔮 Future Research - Longitudinal study of the lean-squad model's effect on release timeliness and quality. - Analysis of contributor pathways from unselected volunteer to future squad lead. - Comparison of representation outcomes under rep-driven vs. squad-embedded team coordination. ### 💡 Implications - Practice: contributors should engage through Make Team Reps and open tasks rather than waiting for squad seats. - Policy: the rep-coordination model becomes the standing governance default for recent cycles. - Security: none stated in this announcement. - Education: clear on-ramps (triage, scrubs, docs) lower the barrier to release participation. - Funding models: sponsors can align hours to defined cycle roles and open tasks. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade roughly 11–13; moderately long sentences with governance vocabulary. #### 👀 Visual learners - Present: structured roster list with linked profiles. - Improve: an org-chart graphic of squad roles and the rep-coordination flow. #### 🔊 Aural learners - Present: none. - Improve: a short audio summary of the squad and cycle model. #### 🗣️ Verbal learners - Present: role labels and named contributors; defined cycle continuity. - Improve: a one-line glossary for "Release Squad," "Make Team Rep," "triage lead." #### 🧩 Kinesthetic learners - Present: links to bug scrubs and contribution paths. - Improve: a step-by-step "join the 7.1 cycle this week" checklist. #### 🧠 Logical learners - Present: clear role hierarchy and continuity reasoning across cycles. - Improve: a RACI table mapping squad roles to responsibilities. #### 🧑‍🤝‍🧑 Social learners - Present: Slack channel and meeting time noted in site chrome; comment thread. - Improve: a kickoff call invite or pairing prompts for new contributors. #### 🧘‍♀️ Solitary learners - Present: self-serve handbook and reports links. - Improve: a self-paced "understand the release cycle" reading path. #### 🌿 Naturalistic learners - Present: none. - Improve: framing the release cycle as a recurring seasonal cadence. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: heading structure and a list of roles with descriptive link text. - Improve: ensure profile links carry full names as accessible text (they do here). #### Keyboard navigation - Present: standard WordPress.org theme with focusable links. - Improve: verify visible focus on share/comment controls. #### Contrast and readability - Present: default Make theme meets 4.5:1 for body text. - Improve: confirm link contrast against background meets AA. #### Text resizing and reflow - Present: responsive theme reflows at 200% zoom. - Improve: confirm the roster list avoids clipping on narrow viewports. #### Media and captions - Not applicable to this source — the post contains no audio or video. #### Forms and interactions - Present: comment/reply controls with login links. - Improve: ensure the comment form fields carry programmatic labels. #### Standards reference - Maps to WCAG 2.2 AA: 1.4.3 Contrast, 2.4.7 Focus Visible, 1.4.10 Reflow, 4.1.2 Name/Role/Value. ### 🌍 DEIB Assessment #### Cultural breadth - Present: a globally distributed contributor roster; note on contributors living "all over the world." - Improve: link localized contribution resources for non-English contributors. #### Inclusive language - Present: gratitude-forward, non-exclusionary framing toward unselected volunteers. - Improve: define insider terms (triage, bug scrub) for first-time readers. #### Neurodiversity support - Present: short paragraphs and a clearly chunked roster. - Improve: add consistent icon+text labels for each role group. #### Representation - Present: a varied, international set of named contributors across roles. - Improve: none required; representation is broad for an announcement. #### Psychological safety - Present: explicit reassurance that unselected volunteers are still valued. - Improve: link a code of conduct reference for new participants. ### ✅ Logical Validity #### Strong reasoning - Analogical/inductive: the post justifies the lean-squad model by citing four prior cycles (6.7–7.0) that used it, supporting continuity. Strong because it generalizes from a consistent track record; could be clarified with outcome metrics from those cycles. - Causal: it claims rep-driven coordination reduces overhead and overlap. Plausible mechanism stated; clarify with before/after workload data. #### Fallacies - Not applicable to this source — an announcement of this kind makes no contested argument, so no notable fallacies are present. #### Tone of voice - Appreciative, collaborative, and celebratory. Examples: "What an outstanding squad," "heartfelt appreciation," "there's a lot to be excited about." ### 🛡️ DARVO Analysis - Not applicable to this source. DARVO describes a defensive rhetorical pattern in response to accusation; this is a neutral, congratulatory announcement with no denial, attack, or victim-offender reversal. ## 🎯 Conclusion - Bottom line: WordPress 7.1's release squad is set, led by Anne McCarthy, continuing the lean-squad model that shifts coordination toward Make Team Reps. - Next steps for readers: follow the [7.1 release page](https://make.wordpress.org/core/7-1/), join #core on Slack, and plug into testing, triage, bug scrubs, or docs if you want to contribute this cycle. ## 🔄 Refactor Appendix — Announcing the WordPress 7.1 Release Squad > Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4). > Defaults: 3 Literature, 1 Permanent. ### 📚 Literature Atoms (H3) #### [H1] WordPress 7.1 squad assembled with Anne McCarthy as lead > [!quote] ID:rw_pending > Release Lead: Anne McCarthy **Context & use**: - Top of the roster list. - Names the cycle's accountable leadership; anchor for tracking 7.1 decisions. **Tags**: #xref **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### [H2] Lean release squad continues the 6.7-through-7.0 model > [!quote] ID:rw_pending > WordPress 7.1 will continue the approach of forming a smaller, focused Release Squad. **Context & use**: - Body paragraph on cycle continuity. - Documents the standing governance pattern for recent releases. **Tags**: #xref **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### [H3] Coordination shifts toward Make Team Reps to cut overhead > [!quote] ID:rw_pending > The goals are to reduce the overhead on the Release Squad while still ensuring each Make Team's contributions and priorities are represented **Context & use**: - Body paragraph explaining the model's rationale. - Captures the explicit tradeoff: less squad overhead, more rep responsibility. **Tags**: #xref **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### [P1] WordPress distributes release coordination to standing team reps **Claim** (one sentence, Courtney's voice): WordPress keeps its release squad small and pushes team representation onto standing Make Team Reps to reduce coordination overhead. **Evidence pointer**: [[#H3]] **Scope & conditions**: Holds for the 6.7–7.1 cycles; breaks if a future cycle reverts to large embedded squads. **Links**: - [[Open-source governance]] — because applies-in release management - [[Volunteer coordination]] — because extends contributor-representation patterns <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Compare release-cycle overhead metrics across 6.7–7.1 to test the lean-squad claim — https://make.wordpress.org/core/7-1/ #fleeting #inbox - [F2] Watch for 7.1 feature-focus announcements to follow this squad post #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Skim the 7.1 release page for milestone dates — research #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Announcing the WordPress 7.1 Release Squad.md|Announcing the WordPress 7.1 Release Squad by make.wordpress.org]] ## Highlights - As with the [6.7](https://make.wordpress.org/core/2024/07/05/wordpress-6-7-planning-proposal-call-for-volunteers/), [6.8](https://make.wordpress.org/core/2024/11/21/wordpress-6-8-call-for-volunteers/), [6.9](https://make.wordpress.org/core/2025/07/11/wordpress-6-9-planning-proposal-and-call-for-volunteers/), and [7.0](https://make.wordpress.org/core/2026/01/09/wordpress-7-0-call-for-volunteers/) release cycles, WordPress 7.1 will continue the approach of forming a smaller, focused Release Squad. This streamlined structure places more emphasis on collaboration with the various [Make Team Reps](https://make.wordpress.org/updates/team-reps/), who are encouraged to help coordinate efforts from within their [respective teams](https://make.wordpress.org/). The goals are to reduce the overhead on the Release Squad while still ensuring each Make Team’s contributions and priorities are represented throughout the cycle, and to reduce overlap between a Make Team Rep and that team’s Release Squad Leads. Noteworthy Contributors will be captured from Team Reps towards the end of the release cycle. ([View Highlight](https://read.readwise.io/read/01kvqqkcjzaryr4pzq2qxqynkp)) - Note: Lean-squad model continues from recent cycles - Tags: atom/literature/h2 - The number of volunteers far exceeded the available squad roles, so we selected folks whose experience and focus best aligned with the needs of the 7.1 release. If you weren’t selected this time, your contributions are still incredibly valuable, and there are plenty of ways to stay involved throughout the release cycle, including testing, bug scrubs, triage, documentation, and more. Every contribution helps move WordPress forward, and we’re grateful for your continued participation. ([View Highlight](https://read.readwise.io/read/01kvqqkekm7ksyde84zd4dk9n9)) - Note: Volunteer demand exceeded leadership seats - Tags: atom/literature/h2