Title: WordPress 6.1 Release Day Process Author: Héctor Prieto Published: October 25, 2022 Last modified: November 1, 2022 --- [ ](https://profiles.wordpress.org/priethor/) [Héctor Prieto](https://profiles.wordpress.org/priethor/) 12:47 am _on_ October 25, 2022 Tags: [6.1 ( 94 )](https://make.wordpress.org/core/tag/6-1/), [core ( 756 )](https://make.wordpress.org/core/tag/core/), [release-process ( 30 )](https://make.wordpress.org/core/tag/release-process/) # WordPress 6.1 Release Day Process [Preparation for WordPress 6.1](https://make.wordpress.org/core/handbook/about/release-cycle/releasing-major-versions/#pre-final-release) final release is underway. This post shares the release process, including the timeline and how you can help. The post will be kept up to date as the release process evolves. ## Release Timeline Overview The current plan is: * The [Dry Run](https://make.wordpress.org/core/handbook/about/release-cycle/releasing-major-versions/#dry-run) started scheduled on [2022-10-31 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221031T1400), but was aborted during triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. as [a blocker](https://core.trac.wordpress.org/ticket/56933) was found. ❌ * [RC6 was launched](https://make.wordpress.org/core/2022/10/31/wordpress-6-1-release-candidate-6-rc6-now-available-for-testing/) to fix the blockerblocker A bug which is so severe that it blocks a release.. 🚀 * The Dry Run was resumed on [2022-10-31 22:30 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221031T2230). ✅ * The 24-hour code freeze started on [2022-10-31 23:29 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221031T2329), at [the end of the Dry Run](https://wordpress.slack.com/archives/C02RQBWTW/p1667259086155729). ⏳ * The[ stable release party](https://make.wordpress.org/core/handbook/about/release-cycle/releasing-major-versions/#release-day) will start on [2022-11-01 23:30 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221101T2330) in the [#core Slack channel](https://wordpress.slack.com/archives/C02RQBWTW). 📅 ## Edit History * October 27th: Dry Run was rescheduled to start earlier,[ as proposed in #6-1-release-leads](https://wordpress.slack.com/archives/C03LZ88NX6G/p1666699778847979). * October 31st: Provided RC6 launch, 24-hour code freeze start time, and release party start time. --- ## Dry Run ✅ [The Dry Run](https://make.wordpress.org/core/handbook/about/release-cycle/releasing-major-versions/#dry-run) is a key event as a final walk-through for the final release. As noted above, the current plan is to start it on [2022-10-31 14:00](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221031T1400). You are invited to observe and/or participate. It’ll happen in the [#core Slack channel](https://wordpress.slack.com/archives/C02RQBWTW). What happens during the dry run? * Review 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. reports to determine if any are critical to warrant another RCrelease 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)](https://make.wordpress.org/core/2022/10/25/wordpress-6-1-release-day-process/?output_format=md#alpha-beta).( 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)](https://make.wordpress.org/core/2022/10/25/wordpress-6-1-release-day-process/?output_format=md#alpha-beta).). * Checks and any necessary updates are made in the `src/wp-admin/includes/update- core.php` file. * Pre-release scripts are run to ensure test suites, coding standards, and other automated checks pass. If the results are acceptable, the release goes into a 24-hour code freeze period. ## 24-Hour Code Freeze⏳ After the dry run and before the release party starts, a mandatory 24-hour code freeze goes into effect. **This locking period started on** **[2022-10-31 23:29](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221031T2329)**. What does this mean? No source code for 6.1.0 (i.e., in the 6.1 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".) can be changed during these 24 hours. What happens if a critical bug is reported during this period? The release squad will meet with committers and maintainers to determine if the issue is a blocker. * If yes, another RC release happens, and the release process restarts (meaning the dry run is repeated, and then the 24-hour code freeze clock restarts). * If not, then the bug is targeted for 6.1.1. ## The Stable Release Party 📅 **The final release will occur on [2022-11-01 23:30](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221101T2330) in [#core](https://make.wordpress.org/core/tag/core/).** The release party on November 1st will start no sooner than 24h after the code freeze starts, with the exact time to be determined accordingly. You are invited to observe and/or participate. It’ll happen in the [#core Slack channel](https://wordpress.slack.com/archives/C02RQBWTW). The release party walks through the steps in the [Major Version Release process](https://make.wordpress.org/core/handbook/about/release-cycle/releasing-major-versions/#release-day) for anyone who wants to follow along. Please note releasing a major version requires more time than releasing a 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. or release candidate. There are more steps in the process. If any last-minute issues need addressing, more time will be needed. ## How You Can Help A key part of the release process is checking that the ZIP packages work on all the different server configurations available. If you have some of the less commonly used servers available for testing (IIS, in particular), that would be super helpful. Servers running older versions of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher and MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. [https://www.mysql.com](https://www.mysql.com/) will also need testing. You can even start this early by running the [WordPress 6.1 RC3 packages](https://wordpress.org/download/releases/#betas), which are built using the same method as the final packages. During the release party, options will be provided on how to help test the release package. ## Tips on What to Test In particular, testing the following types of installs and updates would be much appreciated: * Does a new WordPress install work correctly? This includes running through the manual install process, as well as WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/) or one-click installers. * Test upgrading from 4.0.37, 4.9.22, 5.8.6, 5.9.5, 6.0.3, and 6.1 RC3, as well as any other versions possible. * Remove the `wp-config.php` file and test a fresh install. * Test single site and multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also **network**, **blog**, **site**/networknetwork ( versus site, blog) (both subdirectory and subdomain) installations. * Does it upgrade correctly? Are the [files listed in `$_old_files`](https://core.trac.wordpress.org/browser/branches/5.9/src/wp-admin/includes/update-core.php#L21) removed when you upgrade? * Does multisite upgrade properly? Testing the following user flows on both desktop and mobile would be great to validate each function as expected: * Publish a post, including a variety of different blocks. * Comment on the post. * Install a new pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party./theme, or upgrade an existing one. * Change the site language. * If you’re a plugin developer, or if there are complex plugins you depend upon, test that they’re working correctly. --- _Props to _[@desrosj](https://profiles.wordpress.org/desrosj/) and [@zoonini](https://profiles.wordpress.org/zoonini/) _for peer review._ [#6-1](https://make.wordpress.org/core/tag/6-1/), [#core](https://make.wordpress.org/core/tag/core/), [#release-process](https://make.wordpress.org/core/tag/release-process/) ### Share this: * [ Threads ](https://make.wordpress.org/core/2022/10/25/wordpress-6-1-release-day-process/?share=threads) * [ Mastodon ](https://make.wordpress.org/core/2022/10/25/wordpress-6-1-release-day-process/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/core/2022/10/25/wordpress-6-1-release-day-process/?share=bluesky) * [ X ](https://make.wordpress.org/core/2022/10/25/wordpress-6-1-release-day-process/?share=x) * [ Facebook ](https://make.wordpress.org/core/2022/10/25/wordpress-6-1-release-day-process/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/core/2022/10/25/wordpress-6-1-release-day-process/?share=linkedin) 1. ![](https://secure.gravatar.com/avatar/247c6d64a9cef124d55f50af6588ea5c0b96c59dae02a045a59eab31bc7cd7e5? s=32&d=mm&r=g) 2. [BackuPs](https://profiles.wordpress.org/backups/) 8:51 am _on_ October 27, 2022 3. Hi, I tried the more tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) in the post content but it does not seem to work anymore in any default theme, with or without gutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) active, or in the default text editor. The tag shows but in the front website there is no readmore text link. Am i missing something? 4. Thank you for your time. Comments are closed. # Post navigation [← Editor chat summary: Wednesday, 20 October 2022](https://make.wordpress.org/core/2022/10/24/editor-chat-summary-wednesday-20-october-2022/) [Performance Chat Summary: 25 October 2022 →](https://make.wordpress.org/core/2022/10/25/performance-team-meeting-summary-25-october-2022/)