\n\n\n\n
Thanks to <\/em>@chanthaboune and @cbringmann for helping shape the schedule and release squad, and for peer reviewing this post.<\/em><\/p>\n\n\n\n #6-1<\/p>\n","contentFiltered":" This is a follow-up post for the first WordPress 6.1 Planning Roundup published in this blog on June 23rd<\/a>.<\/p>\n<\/div><\/div>\n\n\n\n The WordPress 6.1 Development Cycle page<\/a> has been published with an updated timeline and release team and will be kept up to date to reflect any further changes to the release cycle.<\/p>\n\n\n\n Based on the feedback received in the first schedule proposal, this updated schedule includes a third betaBeta<\/span> A 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.<\/span><\/span><\/span> release<\/strong> before the release candidaterelease candidate<\/span> 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)<\/a>.<\/span><\/span><\/span> phase, pushing the stable release date one week later to November 1st, 2022<\/strong>. To avoid celebrating the dry run during the widely observed October 31st holidays, the dry run is proposed to take place on October 28th instead but could be adjusted depending on the release squad availability.<\/p>\n\n\n\nRelease Schedule<\/h2>\n\n\n\n