Tag Archives: 6.2

Jb Audras 4:55 pm on May 9, 2023
Tags: 6.2, , ,   

WordPress 6.2.1 RC1 is now available

WordPress 6.2.1 Release Candidate 1 (RC1) is available for testing! Some ways you can help test this minor release:

  • Use the WordPress Beta Tester 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/ or can be cost-based plugin from a third-party.
    • As this is a minor 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). release, select the Point Release channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunk.
  • Use 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/ https://make.wordpress.org/cli/ to test:
    wp core update https://wordpress.org/wordpress-6.2.1-RC1.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

6.2.1 RC1 features 19 fixes on Core as well as 10 fixes for the BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor.

The following coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. are fixed:

  • #57387 – use aligncenter class in about page sub-heading
  • #57903 – Non-core blocks are not properly loading RTL stylesheets
  • #57918 – “Deprecated” on the Appearance Menu page of the classic theme.
  • #57937 – Sync the SECURITY.md file with our HackerOne policy
  • #57994 – Coding Standards fixes for WP 6.2.1
  • 57996 – Change $search_columns type from array to string[].
  • #58007 – HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.: Support comments created by invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. 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.) name in tag closers
  • #58028 – WP_HTML_Tag_Processor: Its reference in the Developer Resources is broken
  • #58051 – Attachment custom fields not rendered after upload
  • #58064 – In the comment_time function, the call to the get_comment_time function is incorrect.
  • #58069 – Performance of _wp_normalize_relative_css_links() can be increased >2x
  • #58096 – Incorrect color for “Theme enabled.” adminadmin (and super admin) notice
  • #58146 – HTML API: Ensure attribute updates happen only once for case variants
  • #58160 – HTML API: Fix case where updates are overlooked when seeking to earlier locations.
  • #58179 – HTML API: Accumulate shift for internal parsing pointer.
  • #58203 – jQuery version doesn’t match
  • #58250 – HTML API: Adjust coding style to pass 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/ linter
  • #58254 – HTML API: Fix ordering issue in docblockdocblock (phpdoc, xref, inline docs) that’s breaking Developer Resources
  • #58274 – Update @wordpress packages for WordPress 6.2.1

The following block editor issues from GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ are fixed:

  • GH 49135 – i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.: Add context to labels related to CSSCSS Cascading Style Sheets. position properties
  • GH 49054 – Comments: Fix ‘sprintf requires more than 1 params’ error
  • GH 49861 – Fix the site editor loading in multi-site installs
  • GH 49881 – Fix quick inserter going off-screen in some situations
  • GH 49685 – Site Editor: Decode the site title properly
  • GH 48210 – Firefox: fix input rules (ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org async state issue)
  • GH 49703 – Only show alignment info when parent layout is constrained
  • GH 49450 – [Inserter]: Fix onHover error on patterns tab in mobile
  • GH 49364 – Fix site editor redirection after creating new template or template part
  • GH 49675 – Site Editor: fix the ‘back to Dashboard’ links labelling

What’s next?

The developer-reviewed workflow (double committer sign-off) is now in effect when making changes to the 6.2 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"..

The final release is expected on Tuesday, May 16th, 2023 (see the release planning). Please note that this date can change depending on possible issues after RC1 is released. Coordination will happen in the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ #6-2-release-leads channel.

A special thanks to everyone who helped test, raised issues, and helped to fix tickets. With this release candidate, testing continues, so please help test!

The WordPress 6.2.1 release is led by @audrasjb, @mamaduka and @sergeybiryukov.

Thanks @costdev and @francina for proofreading.

#6-2, #6-2-1, #minor-releases, #releases

Héctor Prieto 4:30 pm on March 28, 2023
Tags: 6.2,   

WordPress 6.2 release date updated: March 29, 2023

The WordPress 6.2 release was due today, March 28, 2023. However, a regression with date formats has been spotted during the 24-hour freeze. Release leads have agreed to revert the ticketticket Created for both bug reports and feature development on the bug tracker. that introduced the regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5., which will require another 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). version, restarting the 24-hour freeze timer, and a new release date on March 29th.

Ensuring the newest version of WordPress meets the best quality standards and doesn’t introduce a regression that can impact many popular business-oriented plugins is essential.

WordPress 6.2 Release Candidate 5 has been shipped, reverting the following changeset:

Following this 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). release, the 24-hour code freeze timer has been restarted, and the current target release date is 2023-03-29 at 17:00 UTC.

Props to @cbringmann, @costdev,@davidbaumwald, and @hellofromtonya for peer-reviewing this post.

#6-2, #releases

Lauren Stein 5:33 pm on March 23, 2023
Tags: 6.2, ,   

WordPress 6.2 Release Candidate 4

To get ready for the final release of WordPress 6.2 on March 28, 2023, an RC4 has been put together to help cover some last-minute fixes. 

Here’s what’s changed since RC3:

  • Revert changesets [55358] and [55360], restoring the wp_insert_user() function back to its previous state, to avoid a regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. on the related wp_update_user() function (see tickets #57967 and #57394).

Thanks to everyone who has assisted with testing this release. Your feedback and help in filing 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 keep the WordPress experience stable, smooth, and delightful. It’s critical work and a great way to contribute to the project—especially in these final moments before release day.

How to install RC4

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 is recommended that you test RC4 on a test server and site. 

You can test WordPress 6.2 RC4 in three ways:

  • Option 1: Install and activate the WordPress Beta Tester 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/ or can be cost-based plugin from a third-party. (select the “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “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./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). Only” stream).
  • Option 2: Direct download the RC4 version (zip).
  • Option 3: Use the following 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/ https://make.wordpress.org/cli/ command:

    wp core update --version=6.2-RC4

Keep WordPress bug-free—help with testing

Without your testing support, hitting important product milestones would be a much bigger challenge. It’s also a meaningful way to contribute to the project. If you’re new to testing, or it’s been a while, this detailed guide can help you get started. 

If you think you 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 report, you can file one on WordPress Trac. You can also check your issue against a list of known bugs.

Test your plugins and themes

As you test your latest versions against RC4, make sure you update the “Tested up to” version in your plugin’s readme file to 6.2. If you find compatibility problems, please post detailed information to the support forums.

Check out the WordPress 6.2 Field Guide for more details about the major changes in this release.

Help translate WordPress

Do you speak a language other than English? Help translate WordPress into more than 100 languages.

Release the haiku

What’s this? RC4?
Get those fixes out the door
Release day is close

Thank you to the following contributors for collaborating on this post: @audrasjb @hellofromtonya

#6-2, #development, #releases

marybaum 5:46 pm on March 7, 2023
Tags: 6.2, ,   

WordPress 6.2 Beta 5

WordPress 6.2 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. 5 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 5 on a test server and site.

You can test WordPress 6.2 Beta 5 in three ways:

Option 1: Install and activate the WordPress Beta Tester 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/ or can be cost-based plugin from a third-party. (select the “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “Beta/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). Only” stream).

Option 2: Direct download the Beta 5 version (zip).

Option 3: Use the following 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/ https://make.wordpress.org/cli/ command:

wp core update --version=6.2-beta5

The current target for the final release is March 28, 2023, which is three 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.

This is an extra beta

Testing for issues is a critical part of developing any software, and it’s a great way to start contributing to WordPress—now more than ever. This detailed guide is a great place to start if you’ve never tested a beta release.

This beta fixes a newly discovered bug that first appeared in Beta 1 and potentially affected every user who uses the Back button in any major browser. 

The 6.2 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)., which will now happen on Thursday, March 9, depends on your confirmation that this fix works well. So please download and test.

A haiku from the beta-five mind for 6.2

One little 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. found
Beta 5 to test a fix
RC 1 awaits

Thank you to the following contributors for collaborating on this post: @jpantani @cbringmann @davidbaumwald @audrasjb

#6-2, #development, #releases

Jonathan Pantani 5:35 pm on March 1, 2023
Tags: 6.2, ,   

WordPress 6.2 Beta 4

WordPress 6.2 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. 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 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/ or can be cost-based plugin from a third-party. (select the “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “Beta/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). Only” stream).

Option 2: Direct download the Beta 4 version (zip).

Option 3: Use the following 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/ 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 CoreCore 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 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. 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 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/ features? Find out what’s been included since WordPress 6.1 (the last major releasemajor 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 headerHeader 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

Lauren Stein 6:09 pm on February 21, 2023
Tags: 6.2, ,   

WordPress 6.2 Beta 3

WordPress 6.2 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. 3 has arrived and is now 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, you should test Beta 3 on a test server and site.

You can test WordPress 6.2 Beta 3 in three ways:

Option 1: Install and activate the WordPress Beta Tester 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/ or can be cost-based plugin from a third-party. (select the “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “Beta/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). Only” stream).

Option 2: Direct download the Beta 3 version (zip).

Option 3: Use the following 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/ https://make.wordpress.org/cli/ command:

wp core update --version=6.2-beta3

The current target for the final release is March 28, 2023, which is five weeks away. Your support 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.

We Need You… to Test!

Testing for issues is a critical part of developing any software, and it’s a meaningful way for anyone to contribute—regardless of experience level. 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 CoreCore 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 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. report, you can file one on WordPress Trac. You can also check your issue against a list of known bugs. Ready to learn more about 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/ features? Find out what’s been included since WordPress 6.1 (the most recent major releasemajor 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 the currently available 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.

Changes for Beta 3

This phase of the release addresses approximately 34 issues since last week’s Beta 2—props to all you Beta testers out there. Reaching each release milestone would be impossible without your help.

So far, WordPress version 6.2 contains more than 292 enhancements and 354 bug fixes, including more than 258 Trac tickets resolved in the 6.2 milestone. Expect even more fixes as the 6.2 release cycle continues.

Enhancements in the 6.2 release cycle will make this the most modern way yet to build with WordPress. Are you ready to discover a new interface in the Site Editor giving you more control of the creation process? That’s just one of the highlights from the 6.2 release. For more information refer to the Beta 1 announcement for other notable highlights.

Add to Calendar: 6.2 Live Demo

Release squad members @annezazu and @rich will showcase some of the exciting features slated for the 6.2 release. Get a closer look at a Zoom live demo presentation on Thursday 2 March 2023, 17:00 UTC.

A Third Haiku for 6.2

Another week’s here
Beta 3 it’s you and me
Party, download, test

Thank you to the following contributors for collaborating on this post: @jpantani @davidbaumwald

#6-2, #development, #releases

Jonathan Pantani 6:08 pm on February 14, 2023
Tags: 6.2, ,   

WordPress 6.2 Beta 2

WordPress 6.2 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 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, the release squad recommends you test Beta 2 on a test server and site.

You can test WordPress 6.2 Beta 2 in three ways:

Option 1: Install and activate the WordPress Beta Tester 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/ or can be cost-based plugin from a third-party. (select the “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “Beta/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). Only” stream).

Option 2: Direct download the Beta 2 version (zip).

Option 3: Use the following 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/ https://make.wordpress.org/cli/ command:

wp core update --version=6.2-beta2

The current target for the final release is March 28, 2023, which is six 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.

How you can help: testing!

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 CoreCore 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 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. report, you can file one on WordPress Trac. You can also check your issue against a list of known bugs.

Interested in 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/ features? Find out what’s been included since WordPress 6.1 (the last major releasemajor 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 the currently available 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 2

This release contains more than 292 enhancements and 354 bug fixes for the editor, including more than 238 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 71 issues since last week’s Beta 1—courtesy of all you helpful Beta testers out there. (Thanks and keep up the great work!) 

The 6.2 release cycle is full of improvements that the release team is excited for you to test from more easily integrating media from Openverse to an overhauled version of the Navigation block. Styles are getting plenty of attention too with a new Style Book, CSSCSS Cascading Style Sheets. support for your site or blocks, and much, much more. Check out the Beta 1 announcement for more details on other notable highlights.

Another haiku for 6.2

Ready and waiting,
Take a look—it’s Beta 2!
Test it now, won’t you?

Thank you to the following contributors for collaborating on this post: @laurlittle @marybaum @audrasjb @cbringmann @flixos90

#6-2, #development, #releases