WordPress 6.2\u2019s first release candidate (RC1) is here and ready for testing.<\/p>\n\n\n\n
Reaching this part of the release cycle is a key milestone. While we consider release candidates ready for final release, additional testing and use by the community can only make it better.<\/p>\n\n\n\n
The official release of 6.2 is just three short weeks away on March 28. In open source, we say with many eyes, all bugs are shallow<\/a>, so we ask everyone across the WordPress ecosystem\u2014theme and plugin developers, educators, agencies, and creators\u2014to jump in and help test<\/a>.<\/p>\n\n\n\n This version of the WordPress software is under development. <\/strong>Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it is recommended that you test RC1 on a test server and site. <\/p>\n\n\n\n You can test WordPress 6.2 RC1 in three ways:<\/p>\n\n\n\n Option 1<\/strong>: Install and activate the WordPress Beta Tester<\/a> plugin (select the \u201cBleeding edge\u201d channel and \u201cBeta\/RC Only\u201d stream).<\/p>\n\n\n\n Option 2<\/strong>: Direct download the RC1 version (zip)<\/a>.<\/p>\n\n\n\n Option 3<\/strong>: Use the following WP-CLI command:<\/p>\n\n\n\n First-time tester? Here’s a guide to getting started<\/a>.<\/em> <\/p>\n\n\n\n This release includes over 900 enhancements and fixes and is the first major release of 2023. <\/p>\n\n\n\n WordPress 6.2 comes packed with enhancements to make everything you do smoother, faster and a little more inspired:<\/p>\n\n\n\n Want to see some of these featured highlights in action? Check out the WordPress 6.2 Demo<\/a> recorded March 2, 2023.<\/em><\/p>\n\n\n\n Do you crave a deep dive into tech specs? These recent posts cover a few of the latest technical updates. This is not an exhaustive list, but it should get you started: <\/p>\n\n\n\n These are also compiled into a comprehensive WordPress 6.2 Field Guide<\/a>. <\/p>\n\n\n\n Without your testing support, hitting important product milestones would be a much bigger challenge. It\u2019s also a meaningful way to contribute to the project. If it\u2019s your first time, or it\u2019s been a while, this detailed guide<\/a> is a great resource to lean on. <\/p>\n\n\n\n From a global perspective, every time you test a pre-release version, you help secure the future of WordPress. How? By helping the community prove the software is stable, easy to use, and as bug-free as possible. <\/p>\n\n\n\n Want to know more about testing releases in general? You can follow along with the testing initiatives<\/a> that happen in Make Core. You can also join the #core-test channel<\/a> on the Making WordPress Slack workspace<\/a>.<\/p>\n\n\n\n If you think you have run into an issue, please report it to the Alpha\/Beta area<\/a> in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac<\/a>. You can also check your issue against a list of known bugs<\/a>.<\/p>\n\n\n\n Interested in the details on the latest Gutenberg features? Find out what\u2019s been included since WordPress 6.1 (the last major release of WordPress). You will find more details in these What\u2019s new in Gutenberg<\/em> posts for 15.1<\/a>, 15.0<\/a>, 14.9<\/a>, 14.8<\/a>, 14.7<\/a>, 14.6<\/a>, 14.5<\/a>, 14.4<\/a>, 14.3<\/a>, and 14.2<\/a>.<\/p>\n\n\n\n Do you build plugins and themes? Your products play a special role in helping WordPress do more things for more people across the world. In turn, more people in the WordPress Community mean a bigger, more robust open web.<\/p>\n\n\n\n Chances are, you have already been testing your latest versions against the WordPress 6.2 betas. With RC1, you will want to finalize your testing and update the \u201cTested up to\u201d<\/em> version in your plugin\u2019s readme file to 6.2. <\/p>\n\n\n\n If you find compatibility problems, please post detailed information to the support forums<\/a>.<\/p>\n\n\n\n Do you speak a language other than English? \u00bfEspa\u00f1ol? Fran\u00e7ais? Portugu\u00eas? \u0420\u0443\u0441\u0441\u043a\u0438\u0439? \u65e5\u672c? Help translate WordPress into more than 100 languages.<\/a> This release also marks the hard string freeze<\/a> point of the 6.2 release cycle.<\/p>\n\n\n\n Want to know more about what went into the making of WordPress 6.2? Please check out the 6.2 release cycle<\/a>, the Make WordPress Core blog<\/a>, or search for all things 6.2 related<\/a>. <\/p>\n\n\n\n Thank you to the following contributors for collaborating on this post: <\/em>@laurlittle<\/em><\/a> <\/em>@cbringmann<\/em><\/a>, @audrasjb<\/a>, @jpantani<\/a>. Haiku by @nomad-skateboarding-dev<\/a><\/em>.<\/p>\n","protected":false},"excerpt":{"rendered":" WordPress 6.2 Release Candidate 1 is now available for download and testing.wp core update --version=6.2-RC1<\/code><\/pre>\n\n\n\nWhat\u2019s in WordPress 6.2 RC1<\/h2>\n\n\n\n
\n
\n
\n
Let’s go on a bug hunt!<\/h2>\n\n\n\n
A special thanks to WordPress plugin and theme developers<\/h2>\n\n\n\n
Help translate WordPress<\/h2>\n\n\n\n
Hungry for even more?<\/h2>\n\n\n\n
Another haiku for 6.2\u2014it\u2019s tradition! <\/h2>\n\n\n\n
Beta has left us
The code sings such happy songs
Six point two RC<\/pre>\n\n\n\n
\nThis 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 RC 1 on a test server and site.<\/p>\n","protected":false},"author":8210271,"featured_media":14631,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"episode_type":"","audio_file":"","cover_image":"","cover_image_id":"","duration":"","filesize":"","date_recorded":"","explicit":"","block":"","filesize_raw":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[5,14],"tags":[486,184,409],"class_list":["post-14619","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-development","category-releases","tag-6-2","tag-development","tag-releases"],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/wordpress.org\/news\/files\/2023\/03\/WordPress-6.2-RC1.png?fit=1600%2C900&ssl=1","jetpack_shortlink":"https:\/\/wp.me\/pZhYe-3NN","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/14619","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/users\/8210271"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/comments?post=14619"}],"version-history":[{"count":7,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/14619\/revisions"}],"predecessor-version":[{"id":14635,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/14619\/revisions\/14635"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/media\/14631"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/media?parent=14619"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/categories?post=14619"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/tags?post=14619"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}