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 > ## 🧭 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: coo **Exciting News: The** [**WordPress 7.1**](https://make.wordpress.org/core/7-1/) **Release Squad is assembled!** 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. 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. Big thanks to everyone who volunteered for the release squad, and heartfelt appreciation to everyone helping move WordPress 7.1 forward through testing, triage, documentation, bug scrubs, and more. Your efforts make this release possible, and there’s a lot to be excited about as WordPress 7.1 comes together!, Announcing the WordPress 7.1 Release Squad, make.wordpress.org, 01kvqqe03dyz1qszp1vqc9vcnv.