# Announcing the WordPress 7.1 Release Squad **Source doc**: [[3. Resources/Readwise/Articles/Announcing the WordPress 7.1 Release Squad]] > [!question] Lingering Questions > - How does overhead actually compare across the 6.7–7.1 cycles under this lean-squad model — is there a metric anywhere, or is "reduces overhead" asserted? > - What happens to the volunteers who weren't selected — does the pointer to testing/triage/docs work reliably route them into the pipeline, or does it leak people the way the Credits-team retention research (see the Contribution Pipeline note) describes? > [!tip] Article Ideas > - None — this is a procedural announcement, not an angle with independent argument to build on. > [!link] Cross Reference > - [[Open Source Governance MOC]] — a live instance of the standing-representative coordination pattern. > - [[3. Resources/Permanent Notes/A Contribution Pipeline Needs a Defined Next Step After Training]] — the unselected-volunteers pointer here is exactly the "next step after training" problem that note describes, on the release-squad side of the pipeline. > [!quote] Vocabulary > - **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) who now carry more of the cross-team coordination load. ## Author's thesis The WordPress 7.1 release squad continues the lean, focused-squad model used since 6.7: a smaller leadership group with more coordination responsibility pushed onto standing Make Team Reps, trading squad overhead for reliance on the reps to keep each team's priorities represented. ## Key arguments (≤3) 1. **Squad assembled and named**: Anne McCarthy leads as Release Lead, with named Coordination, Tech, Triage, and Test leads. 2. **The model is a repeat, not a change**: 6.7 through 7.0 used the same smaller-squad-plus-team-reps structure; 7.1 continues it deliberately. 3. **The explicit tradeoff**: less overhead on the squad itself, more responsibility on Make Team Reps, with a secondary goal of reducing overlap between a rep and that team's squad leads. ## Claim atoms ### WordPress 7.1 squad assembled with Anne McCarthy as lead > [!quote] ID:rw_wp71_1 > Release Lead: Anne McCarthy Where/why: top of the roster list; names the cycle's accountable leadership and anchors any future tracking of 7.1 decisions. ### Lean release squad continues the 6.7-through-7.0 model > [!quote] ID:rw_wp71_2 > WordPress 7.1 will continue the approach of forming a smaller, focused Release Squad. Where/why: body paragraph on cycle continuity — documents the standing governance pattern for recent releases rather than a one-off choice. ### Coordination shifts toward Make Team Reps to cut squad overhead > [!quote] ID:rw_wp71_3 > The goals are to reduce the overhead on the Release Squad while still ensuring each Make Team's contributions and priorities are represented. Where/why: body paragraph explaining the model's rationale — the explicit tradeoff between squad size and rep responsibility. ## Permanent candidates - **WordPress delegates release coordination to standing team reps** — promoted below as a new note. Generalizes the specific 7.1 squad structure into a governance pattern (rotating leadership plus standing reps to keep overhead low) worth comparing against other volunteer organizations in the vault. ## Processing checklist - [ ] Skim the 7.1 release page for milestone dates - [ ] Compare release-cycle overhead across 6.7–7.1 if any retrospective data surfaces, to test the lean-squad claim rather than take it on assertion - [x] Connect into the relevant MOC — [[3. Resources/MOCs/Open Source Governance MOC]] ## Links - [[3. Resources/MOCs/Open Source Governance MOC]] — release-squad structure is core release-management governance. - [[3. Resources/Permanent Notes/A Contribution Pipeline Needs a Defined Next Step After Training]] — applies-in: the volunteers-not-selected pointer to testing/triage/docs is the same "does the next step actually exist" question that note raises about the Credits program.