Announcing the WordPress 7.0 Release Squad

This post is announcing the formation of the 7.0 release squad after a call for volunteers.

Exciting News: The WordPress 7.0 Release Squad is assembled!

• Release LeadRelease Lead The community member ultimately responsible for the Release.: Matias Ventura
• Release Coordination: Ahmed Kabir Chaion, Amy Kamala, Mary Hubbard
• Tech Leads: Ella van Durpe, Mukesh Panchal, Sergey Biryukov
• Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Leads: Jb Audras, JuanMa Garrido
• Test Leads: Ankit K Gupta, Mary Baum

As with the 6.7, 6.8, and 6.9 release cycles, WordPress 7.0 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, who are encouraged to help coordinate efforts from within their respective teams.  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 RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. and that team’s Release Squad Leads. Noteworthy Contributors will be captured from Team Reps towards the end of the release cycle. A special thank you to the Docs team for already identifying that @sajib1223 and @milana_cap will be leading efforts from their perspective!

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.0 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, bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. 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.0 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.0 comes together!

Props to @annezazu and @desrosj for reviewing this post and @jorbin, @desrosj, @annezazu, and @4thhubbard for helping assemble the 7.0 release squad.

#7-0, #planning