6.5 Release Parties Schedule and Hosts

Greetings from your friendly neighborhood 6.5 release coordinators—@priethor, @akshayar, and @marybaum! Below you will find the same calendar @francina built and used for 6.4, only updated with dates and other details for 6.5.

As we saw with several recent releases, things can change at the last minute. Still, the coordinators are starting to anticipate what could happen; work hard to respect the calendar—what is supposed to happen; and address what will happen in real time going forward, by letting you know of any change promptly.

If you can fill any of those roles, please add your name in the comments, with the date and role, so the three of us can finalize the calendar. It would be great to heave two people with the same access level for each party—then we can help each other if a party takes longer than expected.

Over the last three years or so, squads have aimed to start parties at 16:00 UTC because it does cover a range of time zones. We do have squad members in APAC, so it would be nice to start a little earlier — maybe 14:00 UTC, particularly once daylight time starts to kick in across the world.

For now, let’s think about 14:00 UTC and adjust as needed going forward.

Update February 13, 2024: The release party for 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. 2, on Tuesday, February 20, 2024, will start at 16:00 after a one-hour code freeze.

Please check the Hosting Release Page in the Handbook to read about the different roles.

Thank you for the team effort!

Date/TimeMilestoneHostCommittercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.SecurityMission ControlMarcomms
Tuesday, February 13 at 14:00 UTCBeta 1@priethor (backup @marybaum)@audrasjb@davidbaumwald@davidbaumwald
Tuesday, February 20 at 16:00 UTCBeta 2@marybaum (backup @akshayar)
Tuesday, February 27 at 16:00 UTCBeta 3@akshayar (backup @marybaum)
Tuesday, March 5 at 16:00 UTCRelease 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). 1@marybaum (backup @akshayar)
Tuesday, March 12, at 14:00 UTCRelease Candidate 2@akshayar (backup @marybaum)
Tuesday, March 19 at 16:00 UTCRelease Candidate 3@akshayar (backup @priethor)
Monday, March 25 at 16:00 UTCDry Run@priethor (backup @akshayar)
Tuesday, March 26 at 17:00 *UTCGeneral Release@priethor (backup @akshayar)The whole focus team 💪

General release is scheduled 1 hour later than the Dry Run time to allow for a 24-hour freeze.

Thanks @akshayar and @priethor for the peer review.

#6-5, #core, #release