WordPress 6.2 Planning Roundup

Following up on the WordPress 6.2 planning proposal and based on the feedback and comments received, this post intends to summarize the release schedule and release squad composition for the next major WordPress release.

WordPress 6.2 Schedule

As a reminder, the WordPress 6.2 release cycle introduces a fourth planned betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. to accommodate WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia, providing an extra buffer between the event and two of the biggest release milestones (Beta1 and RC1).

Alpha (trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. open for 6.2 release)October 18, 2022
Beta 1 & Feature FreezeFebruary 7, 2023
Beta 2February 14, 2023
Beta 3February 21, 2023
Beta 4February 28, 2023
Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1March 7, 2023
Release Candidate 2March 14, 2023
Release Candidate 3March 21, 2023
Dry RunMarch 27, 2023
WordPress 6.2 General releaseMarch 28, 2023

WordPress 6.2 Release Squad

Thanks to everybody that volunteered for the release squad! Considering all applications for the different roles, a release team has been assembled with project leadership to ensure all areas are properly covered.

Based on the positive feedback received by the proposal of this new role in the call for volunteers for the release squad, this release will trial a new role — Performance Lead. In this first iteration, the Performance Lead will run early performance testing in WordPress trunk and act as an advisor, flagging performance regressions before they are shipped, helping solve them, and providing guidance to the rest of the release squad on performance-related discussions.

Release LeadRelease Lead The community member ultimately responsible for the Release.: Matt Mullenweg
Release Coordinators: Francesca Marano, Héctor Prieto
CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Co-Leads: Tonya Mork, Jb Audras
Editor Tech Co-Leads: George Mamadashvili, Nik Tsekouras
Core Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Co-Leads: Colin Stewart, Mukesh Panchal
Editor Triage Co-Leads: Anne McCarthy, Nick Diego
Design Lead: Rich Tabor
Documentation Co-Leads: Birgit Pauli-Haack, Femy Praseet, Milana Cap, Abha Thakor
Marketing & Communications Co-Leads: Jonathan Pantani, Lauren Stein, Mary Baum
Test Co-Leads: Robin, Adel Tahri
Performance Lead: Felix Arntz

All release decisions will ultimately be this release team’s to make. However, contributors are more than welcome to follow along with the release process on the #6-2-release-leads Slack channel.

Props to @cbringmann for peer review.

#6-2, #planning