WordPress published three official updates between September 10 and 19, 2025: an experiment affecting the 6.9 release squad, the creation of a Core Program Team to improve cross-team coordination, and a Docs Team participation decision involving a contributor.
Key updates
- September 10: Docs Team member Estela Rueda wrote that the WordPress 6.9 release squad is testing a smaller team without a Docs Lead. A temporary "Docs Liaison" role will cover immediate needs, and the post urged reinstating a dedicated Docs Lead on future releases.
- September 15: A WordPress project post announced a Core Program Team to strengthen coordination across Core. The post explained the role of the new team as documenting shared practices, surfacing roadmaps, and supporting contributor teams. It clarified the team will not set product direction.
- September 19: Docs Team leadership asked contributor Jenni McKinnon to step away for a period, citing comments "out of alignment with the team" and continued posting after private outreach. The stepping away of a team member noted that rejoining could be reconsidered later if appropriate.
Background
The September 10 post framed the 6.9 release as an experiment that removed a Docs Lead from the release squad and introduced a liaison instead. It cautioned that this change could lead to documentation being overlooked during planning and execution.
The September 15 project post positioned the Core Program Team as a coordination layer across Core contributor groups, focused on listening, connecting teams, and reducing friction for contributors. It explicitly separated the team from product decision-making.
The September 19 Docs Team post documented a leadership decision following repeated comments that the team said were inconsistent with its intentions. It stated the team would reassess participation at a later date.
Why it matters
- Release documentation: Removing a Docs Lead in 6.9 raises the risk of gaps or delays in end-user and developer docs, which can affect upgrade planning for site owners, agencies, and plugin or theme developers.
- Coordination: The new Core Program Team aims to streamline cross-team work and clarify shared roadmaps without changing product direction.
- Community governance: The public participation decision underscores team norms and moderation expectations that shape contributor experience.
.svg)
.svg)
.svg)