This post aims to prepare a calendar with the expected start time for each release party and who is involved in the upcoming 6.4 milestones.

As we saw happening with 6.3 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. 1, things can change at the last minute, so expect some flexibility. The release team will do their best to respect the calendar and communicate any change promptly.

If you can fill any of those roles, please add your name in the comments, with the date and role, so that I can finalize the calendar. Having two people with the same access level for each party is also okay. This will allow us to help each other if the party takes longer than expected.

I always proposed 16:00 UTC for release parties because it’s a time that allows us to cover quite a few time zones. However, it does not favour contributors in APAC. I will contact those in that area to see if we have people with enough access to run at least one release party in their time zone.

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

Thank you all for the team effort!

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

Thanks @cbringmann and @metalandcoffee for the peer review.

#6-4, #release