WordPress 6.2 Beta 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. 4 is ready for download and testing!
This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you test Beta 4 on a test server and site.
You can test WordPress 6.2 Beta 4 in three ways:
Option 1: Install and activate the WordPress Beta Tester plugin 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/ or can be cost-based plugin from a third-party (select the “Bleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “Beta/RC 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). Only” stream).
Option 2: Direct download the Beta 4 version (zip).
Option 3: Use the following WP-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/ https://make.wordpress.org/cli/ command:
wp core update --version=6.2-beta4
The current target for the final release is March 28, 2023, which is four weeks away. Your continued help with testing is vital to ensuring everything in this release is the best it can be.
Get an overview of the 6.2 release cycle, and check the Make WordPress Core blog for 6.2-related posts in the coming weeks for further details.
Calling all testers! We need your help
Testing for issues is a critical part of developing any software, and it’s a meaningful way for anyone to contribute—whether you have experience or not. This detailed guide is a great place to start if you’ve never tested a beta release.
If you build products for WordPress, you probably realize that the sooner you can test this release with your themes, plugins, and patterns, the easier it will be for you to offer a seamless experience to your users.
Want to know more about testing releases in general? You can follow along with the testing initiatives that happen in Make Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. You can also join the #core-test channel on the Making WordPress Slack workspace.
If you think you may have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug 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. report, you can file one on WordPress Trac. You can also check your issue against a list of known bugs.
Interested in the details on the latest Gutenberg 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/ features? Find out what’s been included since WordPress 6.1 (the last major release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. of WordPress). You will find more details in these What’s new in Gutenberg posts for 15.1, 15.0, 14.9, 14.8, 14.7, 14.6, 14.5, 14.4, 14.3, and 14.2.
What’s new in Beta 4
This release contains more than 292 enhancements and 354 bug fixes for the editor, including more than 286 tickets for the WordPress 6.2 core. Expect even more fixes as the 6.2 release cycle continues.
This phase of the release addresses approximately 79 issues since last week’s Beta 3—props to all the Beta testers out there. (Without you these releases couldn’t happen, so great job, and thank you!)
Discover 6.2 enhancements such as the new collections of header The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. and footer patterns that make creating with WordPress smoother than ever before. There’s plenty more in this release so check out the Beta 1 announcement for more details on other notable highlights.
“Four” you another haiku for 6.2
Time for soft string freeze
Loose ends of Beta 3 tied
Beta 4 for all
Thank you to the following contributors for collaborating on this post: @laurlittle and @davidbaumwald
Haiku by @shilpashah
#6-2, #development, #releases