WordPress 6.0 Retrospective Recap

This post seeks to summarize the feedback received from the 6.0 retrospective, shared on May 27th. Thank you to the eight people who took the time to share their feedback and to those who also did so publicly on the post itself. To keep the post succinct, some non-actionable feedback has been consolidated. 

Please keep in mind that these are just suggestions and things to consider for the future rather than items that will be implemented later. 

What would you keep?

Outside of the following, there were repeat mentions of how collaborative, kind, and communicative the squad was as a whole in answering pings, making decisions, and supporting each other. 

  • Early sharing of the feature highlight grid to influence About page, release video, etc. 
  • Weekly check-ins.
  • Dedicated release channel for coordination.
  • Redundancy with co-leads in various roles to allow for more focus on details, higher capacity for work, etc. 
  • Lack of heroic efforts and last-minute dashes
  • Collaborative decision making, e.g. with regard to the WebFonts 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.
  • Structured release parties 

What would you add?

  • More support for Docs & Training resources, matching devs that worked on issues with those writing docs/training.
  • Clearer documentation around resolving tricky issues during a release and when to bring leadership in.
  • Consider having apprenticeship roles for release squad roles to create a backup and for the continuity of the project. 
  • A reimagined About page that designers can build directly using blocks.
  • Improved automations, specifically for the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Lead role. 
  • Release squad should be picked as early in the release process as possible to allow time to prepare.
  • Consider adding documentation lead role for End User documentation 
  • Improve process for identifying items that need dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase., including labeling of PRs that need dev notes, considering multiple types of flags (DevNotedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. / MiscDevNote / Field guideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page.), ensuring documentation is in place for what needs dev notes, and implementing automation to collect all items. 
  • Checklist for each member of the squad at each release phase for improved coordination. 

What would you remove?

  • Confusion/concerns around the Webfonts API situation. 
  • Confusion around the initial 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. 1 post and what role everyone played. This was very quickly resolved. 
  • Backporting months worth of 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/ PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher changes before the release. 
  • Lack of decisions and process around stabilizing and introducing experimental APIs, leading to a backlog.
  • Improving the process of introducing, stabilizing, and phasing.
  • Secrecy around jazzer leading to a lot of complexity around release time.
  • Too many places for tracking documentation updates from the docs team.
  • Complicated process for dev notes, including recommendations to stop using comments on the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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 be the repository owner. https://github.com/ DevNote tracking issue for collecting all dev notes and change deadline to Beta 1 to give docs team more time.
  • Implementing a feature freeze in Gutenberg a week earlier to leave more room for integration with WordPress Core and reduce the length of beta releases.
  • Share more marcoms around the behind the scenes work with performance and accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) so the UIUI User interface changes aren’t over indexed on messaging wise. 

How did the collaboration feel?

This section included ways for one to indicate how much they agreed or disagreed with a statement around collaboration.

Collaborating on this release was easy results

Pie chart showing that 62.5% of people strongly agree, 25% slightly agree, and 12.5% slightly disagree that collaborating was easy.

Collaborating on this release was enjoyable results

Pie chart showing that 75% of people strongly agree and 25% slightly agree that collaborating was enjoyable.

Collaborating on this release was efficient results

Pie chart showing that 50% of people strongly agree, 12.5% slightly agree, and 37.5% slightly disagree that collaborating was efficient.

Collaborating on this release was well organized results

Pie chart showing that 50% of people strongly agree, 37.5% slightly agree, and 12.5% slightly disagree that collaborating was well organized.

The release process was transparent and easy to follow

Pie chart showing that 37.5% of people strongly agree, 37.5% slightly agree, and 25% were neutral that the release process was transparent and easy to follow.

Would you like to be a part of future squads?

87.5% of people said “I have been part of the release squad and I will gladly repeat”. 12.5% of people said “I haven’t been part of the squad but I would like to try in the future”.

Next Steps

At a high level, a few discussions and follows up have already occurred that others can participate in: 

  • A follow up post was done since the retrospective sharing improvements and automations for the Core Editor release role in light of the experience of those this release cycle. 
  • An open discussion is underway around how best to backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. PHP changes. 
  • An open discussion is underway on the topic of improving ad clearing part of the backlog for experimental APIs. 

Outside of the above, it’s clear that there are some process improvements particularly around documentation to consider including a role for End User documentation, changing the way documentation updates are tracked across multiple places, and the way in which dev notes are wrangled. 


If you are interested in being a part of 6.1’s release squad and working to improve the experience, please share in the comments of the 6.1 planning post. 

Thank you to @davidb @zieladam for reviewing.

#6-0, #retrospective

WordPress 6.0.1 RC 1 is now available

WordPress 6.0.1 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). 1 (RC1) is available for testing! Some ways you can help testing WordPress 6.0.1 RC1:

  • 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 ReleaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunk.
  • Use WP-CLI to test: wp core update https://wordpress.org/wordpress-6.0.1-RC1.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

6.0.1 Release Candidate 1 features 11 bug fixes on Core, as well as 18 bug fixes (view PRs merged in June & July) 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:

  • #55668 – Build/Test Tools: Pass GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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 be the repository owner. https://github.com/ Actions environment variables to the Docker container.
  • #55681 – Fix block-templates theme support not present in /themes REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. endpoint
  • #55808 – About page: Replace video thumbnail image
  • #55837 – Resolve WP_Term_Query cache problem
  • #55890 – Fix caching issues in WP_Term_Query class.
  • #55997 – Remove meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. from oembed allow list
  • #56093 – Register Comments Query LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. from metadata to enable title and description translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization..
  • #56097 – Themes: Revert the change of theme preview width on Add Themes screen.
  • #56126 – Block Patterns: Update the value used for keywords.
  • #55810 – Bundled Themes: Revert the Twenty Ten theme version to 3.6.

The following block editor issues from GitHub are fixed:

  • #41423 – Lower the priority of the gallery gap css so it loads after the block layout css
  • #41487 – Add utility classnames back to blocks that have layout attributes specified
  • #41354 – Block Library: Fix JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. Error in AvatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name. Block
  • #40329 – Media & Text: Remove font size declaration from template
  • #41631 – Comment Author and Date blocks: aligned editor markup with the frontend
  • #41328 – Handle no variation case in the block transform menu
  • #40710 – Fix/block metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. icon prop errors
  • #40593 – Prevent opening the links in editor for Latest Posts
  • #40671 – Navigation block “Open on click”: Inherit font style and font weight
  • #41627 – Comments Block: fixed issue with custom font sizes and links color
  • #40560 – Reuse code of the editor placeholder across Post Comments and Post Comments Form
  • #40563 – Improve the logic for warnings for Post Comments Form placeholder
  • #41603 – Post Comments Form: Add button that enables commenting to warning
  • #40799 – Ensure only the main query is modified when resolving template for new posts
  • #40859 – Strip whitespaces in render_block_core_cover before injecting the featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts..
  • #41827 – Post Template: Ensure layout classnames are not attached to inner li elements
  • #41907 – Pasting: Fix performance 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. due to removeWindowsFragments
  • #42131 – Post Comments Form: Fix warning 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.

What’s next?

The dev-reviewed workflow (double committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. sign-off) is now in effect when making changes to the 6.0 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"..

As per the proposed WordPress 6.0.1 schedule, the final release is expected on Tuesday, July 12th, 2022. 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-0-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.0.1 release is led by @sergeybiryukov @zieladam.

#6-0, #6-0-1, #minor-releases, #releases

A Week in Core – June 27, 2022

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between June 20 and June 27, 2022.

  • 49 commits
  • 43 contributors
  • 71 tickets created
  • 9 tickets reopened
  • 44 tickets closed

The Core team is currently working on the next 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., WP 6.1 and on the next minor, WP 6.0.1 🛠

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Application Passwords

  • Ensure long passwords don’t break the “new password” notice – #54581

Build/Test Tools

  • Add missing @covers tags and fix the docs for the Cron test group – #39265
  • Add missing @covers tags for the AJAX test group – #39265
  • Adjust 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/. notifications logic to account for expected non push events – #55652
  • Allow changes to the code coverage workflow to run on pull request – #55652
  • Configure Xdebug modes in the local Docker environment – #56022
  • Fix erroneous file name, from convertInvalidEntries.php to convertInvalidEntities.php#55652
  • Return an error when uploading a test coverage report fails – #55652
  • Update 3rd party GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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 be the repository owner. https://github.com/ Actions – #55652
  • Update NPM devDependencies to their latest versions – #55652
  • Update the actions/cache action – #55652
  • Always include the error message in assertNotWPError() and assertNotIXRError()#55652
  • Correct the expected result for wp_ajax_replyto_comment() test with a draft post – #39265
  • Further improve Tests_Image_Functions::test_wp_crop_image*() tests – #55652
  • Give the tests for adding empty post metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. values more consistent names – #55652
  • Improve Tests_Image_Functions::test_wp_crop_image*() tests – #55652
  • Improve the test for sticky posts not being moved to the front in sitemaps – #55633
  • Move assertQueryTrue() closer to the other custom assertions in WP_UnitTestCase_Base#55652
  • Put @covers tags before @params in Ajax and Formatting groups – #39265
  • Refactor Tests_Image_Functions::test_load_directory() to split the tests and use a data provider – #55652
  • Remove multiple $wpdb::placeholder_escape() calls in wpdb tests – #55652
  • Replace esc_url_raw() calls with sanitize_url()#39265, #55652
  • Use consistent punctuation in failure messages in Tests_Image_Functions#55652
  • Use more consistent wording when referring to PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher deprecation notices – #55652

Code Modernization

  • Remove dynamic properties in Tests_*_Slashes#56033
  • Remove dynamic properties in Tests_Media#56033
  • Use the integer portion of an item position in add_submenu_page()#55656, #54798

Comments

  • Add contextual autocomplete attributes to comment form fields – #55779

Database

  • Add %i placeholder support to $wpdb->prepare to escape table and column names – #52506
  • Add missing @since mention in get_posts_query_args()#55633
  • Correct the return type for wp_save_image_file()#55646
  • Improve documentation for WP_Image_Editor::save() and related functions – #55646
  • Use third-person singular verbs for function descriptions in Bookmark related files, as per docblockdocblock (phpdoc, xref, inline docs) standards – #55646
  • Use third-person singular verbs for function descriptions in Tests_Image_Functions, per the documentation standards – #55646
  • Use third-person singular verbs for function descriptions in Tests_Sitemaps_wpSitemapsPosts, as per docblock standard – #55646
  • Use third-person singular verbs for function descriptions in the Feed 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., as per docblock standards – #55646

Editor

  • Add utility classnames back to blocks that have layout attributes specified – #56058
  • Universalize functions for checking 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 status – #51819

Embeds

  • Remove MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. as an oEmbed source since the related endpoint has been deprecated – #55997

External Libraries

  • Upgrade PHPMailer to version 6.6.3 – #56016

General

  • Revert an earlier define of the WPINC constant in src/index.php#54233

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.

  • Correct and improve inline docsinline docs (phpdoc, docblock, xref) and tests for functionality related to nooped plurals – #55646, #55652

Media

  • Use correct escaping function for URLs in some legacy media functions – #56064

Posts, Post Types

  • Add caching to _find_post_by_old_slug and _find_post_by_old_date functions. – #36723

REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.

  • Move all links to prepare_links method in theme REST API controller – #56018

Sitemaps

  • Remove duplicate sticky Posts from Sitemap Post Query – #55633

Themes

  • Add actions to template loading to assist with collecting debug info – #54541

Upgrade/Install

  • Add a conditional to facilitate testing of the Rollbacks feature project – #56057, #51857, #54166

Props

Thanks to the 43 people who contributed to WordPress Core on Trac last week: @jrf (9), @SergeyBiryukov (9), @costdev (5), @hellofromTonya (4), @pbeane (4), @antonvlasenko (4), @ironprogrammer (4), @audrasjb (4), @peterwilsoncc (4), @afragen (3), @johnbillion (3), @mukesh27 (2), @Spacedmonkey (2), @desrosj (2), @swissspidy (2), @pbiron (2), @dd32 (1), @pbearne (1), @jorbin (1), @ethitter (1), @flixos90 (1), @tabrisrp (1), @rmccue (1), @RavanH (1), @aristath (1), @zieladam (1), @yannielsen (1), @craigfrancis (1), @davidbaumwald (1), @juliemoynat (1), @bhrugesh96 (1), @sabernhardt (1), @tellyworth (1), @iandunn (1), @apokalyptik (1), @hasanuzzamanshamim (1), @smit08 (1), @glendaviesnz (1), @andrewserong (1), @matveb (1), @samikeijonen (1), @Presskopp (1), and @Synchro (1).

Congrats and welcome to our new contributor of the week: @yannielsen ♥️

Core committers: @sergeybiryukov (24), @desrosj (7), @audrasjb (7), @azaozz (4), @davidbaumwald (2), @johnbillion (2), @spacedmonkey (2), and @jorbin (1).

#6-0, #core, #week-in-core

A Week in Core – June 20, 2022

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between June 13 and June 20, 2022.

  • 52 commits
  • 31 contributors
  • 51 tickets created
  • 8 tickets reopened
  • 37 tickets closed

The Core team is currently working on the next 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., WP 6.1 🛠

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Build/Test Tools

  • Adjust 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/. notifications logic to account for expected non push events – #55652
  • Add a helper method for for creating named data providers in WP_UnitTestCase_Base#55652
  • Add a unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.1 deprecation notice in wp_user_settings()#54914
  • Always include the error message in assertNotWPError() and assertNotIXRError()#55652
  • Consistently check that an image was loaded in image saving tests – #55652
  • Further improve Tests_Image_Functions::test_wp_crop_image*() tests – #55652
  • Improve Tests_Image_Functions::test_wp_crop_image*() tests – #55652
  • Move helper functions in Tests_Image_Functions to more appropriate places – #55652
  • Move the filter_image_editor_output_format() helper method next to the test it’s used in – #55652
  • Re-enable failing REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. test for update_post_parent_caches()#55593
  • Refactor Tests_Image_Functions::test_inferred_mime_types() to use a data provider – #55652
  • Refactor Tests_Image_Functions::test_is_displayable_image_negative() to use a data provider – #55652
  • Refactor Tests_Image_Functions::test_is_displayable_image_positive() to use a data provider – #55652
  • Refactor Tests_Image_Functions::test_is_image_negative() to use a data provider – #55652
  • Refactor Tests_Image_Functions::test_is_image_positive() to use a data provider – #55652
  • Refactor Tests_Image_Functions::test_load_directory() to split the tests and use a data provider – #55652
  • Refactor Tests_Image_Functions::test_mime_overrides_filename() to use a data provider – #55652
  • Refactor Tests_Image_Functions::test_wp_save_image_file() to use a data provider – #55652
  • Remove redundant skip call in Tests_Image_Functions::get_image_editor_engine_classes()#55652
  • Rename classes in phpunit/tests/option/ per the naming conventions – #55652
  • Rename some test methods in Tests_Image_Functions for consistency – #55652
  • Reorder is_gd_image() test methods for consistency – #55652
  • Some improvements for REST API cache priming – #55593, #55652
  • Temporarily disable the failing REST API test for update_post_parent_caches()#55593
  • Use assertSameSets() in some newly introduced tests – #55652
  • Use consistent punctuation in failure messages in Tests_Image_Functions#55652
  • Use more consistent wording when referring to PHP deprecation notices – #55652

Bundled Themes

  • Twenty Nineteen: Ensure custom text color is reflected in the Editor for Quote 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.#55992
  • Twenty Twenty-One: Ensure custom text color is reflected in the Editor for Quote block – #55989

Coding Standards

Database

  • Don’t translate the “WordPress database error” message in the error log – #53125

Docs

  • Add @since notes for html5 theme feature changes in add_theme_support()#51657, #55646
  • Add a comment for stripping the leading AND from SQL clauses in some query classes – #55646
  • Add a missing word in pre_months_dropdown_query filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. description – #55646
  • Consistently declare the $wp_query global in link template functions – #43164
  • Use third-person singular verbs for function descriptions in Tests_Image_Functions, per the documentation standards – #55646
  • Use third-person singular verbs for function descriptions in the Feed 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., as per docblockdocblock (phpdoc, xref, inline docs) standards – #55646
  • Use third-person singular verbs for function descriptions in the TaxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. Administration API – #55646
  • Use third-person singular verbs for function descriptions in the WP_Screen API – #55646

Embeds

  • Remove MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. as an oEmbed source since the related endpoint has been deprecated – #55997

External Libraries

  • Upgrade PHPMailer to version 6.6.2 – #55976
  • Upgrade PHPMailer to version 6.6.3 – #56016

General

  • Use WPINC as a shorter reference to wp-includes in some files – #54233

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.

  • Correct and improve inline docsinline docs (phpdoc, docblock, xref) and tests for functionality related to nooped plurals – #55646, #55652
  • Use a translatable string for displaying a user’s first name and last name – #17025

REST API

  • Avoid duplicated query in post collections – #55677
  • Prime caches for featured images in post controller – #55592
  • Prime caches for linked objects in menu item REST API controller – #55620
  • Prime caches for post parents in post REST API controller – #55593
  • Some documentation and test improvements for update_menu_item_cache()#55620
  • Some documentation and test improvements for update_post_parent_caches()#55593

Taxonomy

  • Fix caching issues in WP_Term_Query class – #55837

Props

Thanks to the 31 people who contributed to WordPress Core on Trac last week: @jrf (15), @peterwilsoncc (4), @SergeyBiryukov (4), @spacedmonkey (4), @TimothyBlynJacobs (3), @mitogh (3), @furi3r (3), @audrasjb (3), @evildon (2), @malthert (2), @hellofromTonya (2), @oztaser (1), @denishua (1), @georgestephanis (1), @gdetassigny (1), @Spacedmonkey (1), @jnz31 (1), @knutsp (1), @mukesh27 (1), @ayeshrajans (1), @bobbingwide (1), @madpixels (1), @nithi22 (1), @kajalgohel (1), @jyolsna (1), @sabernhardt (1), @mt8.biz (1), @adamsilverstein (1), @Synchro (1), @swissspidy (1), and @costdev (1).

Congrats and welcome to our 5 new contributors of the week: @evildon, @gdetassigny, @madpixels, @nithi22, @jyolsna ♥️

Core committers: @sergeybiryukov (37), @audrasjb (6), @spacedmonkey (6), @desrosj (2), and @johnbillion (1).

#6-0, #core, #week-in-core

A Week in Core – June 13, 2022

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between June 6 and June 13, 2022.

  • 27 commits
  • 48 contributors
  • 45 tickets created
  • 10 tickets reopened
  • 36 tickets closed

The Core team is currently working on the next 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., WP 6.1 🛠

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Build/Tests Tools

  • Add a unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.1 deprecation notice in wp_user_settings()#54914
  • Correct an assertion in wp_rand() tests – #55194
  • Move helper functions in Tests_Image_Functions to more appropriate places – #55652
  • Move the tests for individual pluggable functions into their own directory – #55652
  • Re-initialize WP_Rewrite before running wp_list_authors() tests – #55652
  • Rename classes in phpunit/tests/option/ per the naming conventions – #55652
  • Rename classes in phpunit/tests/user/ per the naming conventions – #55652
  • Rename the test file and class for wp_list_authors() tests – #55652
  • Use a consistent URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org in HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. response cookie tests – #51568
  • Use more consistent wording when referring to PHP deprecation notices – #55652
  • Use more descriptive names for wp_rand() test methods – #55194

Bundled Themes

  • Twenty-Twenty: Fix a width/alignement issue on “Wide Line” Separator style variation – #53643
  • Twenty-Twenty: Fix paragraph 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. alignment issues when used on a RTL website – #49447
  • Twenty-Twenty: Improve Quote block style consistency between front and back-end – #55931

Code Modernization

  • Pass correct default value to setcookie() in wp_user_settings()#54914

Docs

  • Correct method reference format in some DocBlocks – #55928
  • Use third-person singular verbs for function descriptions in the Core Translation 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.#55646
  • Use typed array notation in some post function DocBlocks: – #55646
  • Various fixes in wp-includes/pluggable.php docblocks, as per documentation standards – #55646

General

  • Ensure wp_rand() returns 0 when $min and $max values are equal to 0#55194

Media

  • Add decoding="async" to image attributes – #53232
  • Some documentation and test improvements for wp_img_tag_add_decoding_attr()#53232

Query

  • Prime users cache in WP_Query and post REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. controller – #55716
  • Add a hook to filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. author full name from wp_list_authors()#17025
  • Some documentation and test improvements for update_post_author_caches(): – #55716

REST API

  • Improve post cache priming in WP_REST_Post_Search_Handler class – #55674

Text Changes

  • Improve consistency of adminadmin (and super admin) error notices in wp-admin/options.php#50785

Props

Thanks to the 48 people who contributed to WordPress Core on Trac last week: @audrasjb (5), @peterwilsoncc (4), @spacedmonkey (3), @jrf (2), @costdev (2), @sabernhardt (2), @TimothyBlynJacobs (2), @mlajo (1), @acoulombe (1), @azouamauriac (1), @swissspidy (1), @tobifjellner (1), @marekdedic (1), @SergeyBiryukov (1), @kjellr (1), @sergiomdgomes (1), @matthiaspabst (1), @amirkamizi (1), @mayankmajeji (1), @ianbelanger (1), @hasanuzzamanshamim (1), @kajalgohel (1), @iamjaydip (1), @whaze (1), @mukesh27 (1), @westonruter (1), @michaelbourne (1), @mitogh (1), @afercia (1), @shenyanzhi (1), @meysamnorouzi (1), @kevinB (1), @wonderboymusic (1), @DrewAPicture (1), @nacin (1), @Mte90 (1), @jorbin (1), @rafiahmedd (1), @mihai2u (1), @furi3r (1), @adamsilverstein (1), @ayeshrajans (1), @flixos90 (1), @hellofromtonya (1), @isaumya (1), @ocean90 (1), and @dd32 (1).

Congrats and welcome to our 6 new contributors of the week: @mlajo, @acoulombe, @matthiaspabst, @shenyanzhi, @meysamnorouzi, @isaumya ♥️

Core committers: @sergeybiryukov (16), @audrasjb (8), @spacedmonkey (2), and @peterwilsoncc (1).

#6-0, #core, #week-in-core

A Week in Core – June 6, 2022

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between May 30 and June 6, 2022.

  • 23 commits
  • 24 contributors
  • 65 tickets created
  • 3 tickets reopened
  • 41 tickets closed

The Core team is currently working on the next 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., WP 6.1 🛠

Worth noting that the WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe 2022 contributors day gathered more than 800 contributors in Porto last week. This was the largest Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. ever held!

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Build/Test Tools

  • Add some test cases for path_join() with Windows paths – #55897
  • Add unit tests for path_join()#55897
  • Clean up test images before performing assertions in image resize tests – #55652
  • Consistently pass the $force_delete parameter to wp_delete_attachment()#55652
  • Correctly confirm the previous workflow run was triggered by a push event – #55652
  • Don’t overwrite image metadata in a wp_calculate_image_srcset() test for zero width – #55652
  • Prevent inaccurate “fixed” notifications in 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/.#55652
  • Require the zip PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher extension in 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. templates export file test – #55652
  • Update the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org to the documentation on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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 be the repository owner. https://github.com/ Actions environment variables – #55652

Bundled Themes

  • Twenty-Twenty: Alignment fix on Separator Block editor styles – #55896
  • Twenty-Twenty: Fix paragraph block alignment issues when used on a RTL website – #49447
  • Twenty-Twenty: Improve Quote block style consistency between front and back-end – #55931

Docs

  • Correct method reference format in some DocBlocks – #55928
  • Replace “updated” with “deleted” in wpdb::delete return description – #55646
  • Use third-person singular verbs for method descriptions in wp-includes/post.php, as per docs standards – #55646
  • Various fixes in wp-includes/pluggable.php docblocks, as per documentation standards – #55646

Formatting

  • Make sanitize_url() the recommended function for sanitizing a URL – #55852

General

  • Ensure wp_rand() returns 0 when $min and $max values are equal to 0#55194
  • Remove redundant ltrim() from path_join()#55897
  • Replace all esc_url_raw() calls in core with sanitize_url()#55852

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.

  • Use consistent context for the “Add New” string when referring to media – #55876

Media

  • Add support for WebP images in the Thickbox library – #55786

Text Changes

  • Improve consistency of adminadmin (and super admin) error notices – #50785

Props

Thanks to the 24 people who contributed to WordPress Core on Trac last week: @SergeyBiryukov (5), @audrasjb (4), @mukesh27 (3), @benjgrolleau (3), @sabernhardt (2), @peterwilsoncc (2), @iamjaydip (2), @whaze (2), @karlijnbk (2), @amirkamizi (1), @larrach (1), @ilunabar (1), @tobifjellner (1), @mihaidumitrascu (1), @transl8or (1), @cadlec (1), @umesh84 (1), @joyously (1), @mayankmajeji (1), @dd32 (1), @kajalgohel (1), @hasanuzzamanshamim (1), @ianbelanger (1), and @graham73may (1).

Congrats and welcome to our 6 new contributors of the week: @benjgrolleau, @whaze, @karlijnbk, @amirkamizi, @mihaidumitrascu, @cadlec ♥️

Core committers: @sergeybiryukov (13), @audrasjb (8), and @desrosj (2).

#6-0, #core, #week-in-core

WordPress 6.0 ‘Arturo’ Retrospective

With WordPress 6.0 out in the world, it would be very helpful to this and future release squads if all those involved in contributing could take some time to reflect and share our thoughts on the release process to learn, iterate, and make future releases smoother. ✨

Anyone is welcome to participate in this retro, so please take a few moments to fill in the form or leave public feedback in the comments below. The survey is not anonymous if I need to reach out for further clarification, but your email address will not be shared or used for any other purpose.

To accommodate for WCEU2022 taking place next week the form and comments will be open until June 19, 2022. The results will be reviewed and summarized in a follow-up post in this same blogblog (versus network, site) in late June 2022.

Thank you, everyone, for your contribution to this release, and thanks in advance for taking the time to help make future releases even better!


Props to @annezazu for peer review

#6-0 #retrospective

Dev Chat Summary, May 25, 2022

Agenda followed for the weekly WordPress Developers Chat. The meeting was facilitated by @annezazu.

Start of the meeting in #Core channel on the Make WordPress 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/..

2. Announcements

  • WordPress 6.0 “Arturo” was released yesterday! Big props to all involved.
  • The dry run for the WordPress 6.0 Release took place on May 23, followed by a 24-hour code freeze.
  • WordPress 6.0 RC4 was released over the last week on May 20, 2022.

If you haven’t seen it yet, here is a great video covering the latest release:

If anyone is wondering how that amazing video was made, it is a combination of Figma storyboards and motion design in After Effects.

3. Blogblog (versus network, site) posts of note

  • 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/ 13.3 is in the process of being released today as we speak.
  • The latest core editor improvement post on container blocks and 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. locking shows off some new features to explore with row/stack/group.
  • A recap of the latest hallway hangout happened this morning on FSE topics and might be of interest to folks here.

Next week, there will be a doubled up version of “This week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.” too.

4. Upcoming releases

With 6.0 just out the door, the focus turns to both 6.0.x and 6.1. Initial steps have been taken following the post release items in the handbook so stay tuned for more! Currently, a project board is open for 6.0.1 in case anyone likes to follow the details: https://github.com/orgs/WordPress/projects/31

There is only one reported issue so far and @annezazu, as co-release coordinator will be checking with other teams for any other issues reported with 6.0.

5. Component maintainers

Build/Test Tools reported by @sergeybiryukov:

  • GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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 be the repository owner. https://github.com/ Action Slack notifications now link to a specific run attempt. This makes it easier for someone to see the proper context of a specific notification in case of failure. See ticketticket Created for both bug reports and feature development on the bug tracker. #55652 for more details. Thanks @desrosj
  • Some instabilities (test leaks) were fixed in unit tests for comments. See ticket #54725 for more details. Thanks @hellofromtonya
  • General: The recommended minimum version for MariaDB was bumped to 10.3. See ticket #55791 for more details. Thanks @hellofromtonya, again! 
  • Date/Time, 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., Permalinks: No major news this week

Update/install reported by @afragen

Sitemaps component reported by @pbiron:

  • There is one ticket ready to commit for 6.1, #55633

6. Open floor

@audrasjb prepared some great stats on WordPress 6.0 contributors.

@hifidesign brought up a PR that documents pretty big 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. w/r/t to unnecessary duotone code being added to non-FSE themes #38299 and @annezazu mentioned that all of the work is being tracked in that ticket for anyone to follow up.

@afragen has a list of tickets that need a committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. review:

@pbironmentioned that the non-direct filesystem classes are difficult to test because it is often hard to set up a testing environment to test them. There is a proposal on the works to do a review/improvements of the various WP-Filesystem classes.

Props to: @estelaris for writing the summary and @annezazu for reviewing.

#6-0, #dev-chat, #summary

Dev Chat Agenda, May 25, 2022

(Republishing)

This weekly WordPress Developers Chat takes place in the #Core channel of the Make WordPress 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/. on Wednesday May 25, 2022 at 20:00 UTC. All welcome.

1. Welcome

Dev Chat summary from the meeting on May 18, 2022

2. Announcements

It has been a very busy week! Thanks to everyone who has been involved from across the project and the Release Squad too.

WordPress 6.0 “Arturo” was released yesterday!

The dry run for the WordPress 6.0 Release took place on May 23, followed by a 24-hour code freeze.

WordPress 6.0 RC4 was released this week too on May 20, 2022.

3. Blogblog (versus network, site) posts of note

There will be a bumper edition of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. next week!

4. Upcoming releases

a) WordPress 6.0

Updates from Release Co-ordinators and members of the squad.

b) WordPress 6.1

5. Open floor

If you have any items for Open Floor, please add them in the comments below.

If you are a component maintainer and wish to raise a ticketticket Created for both bug reports and feature development on the bug tracker. in dev chat or give an update, you can also add information in the comments section.

Thanks to @nalininonstopnewsuk and @marybaum for working on the agenda and planning,
and to @estelaris for volunteering to do the notes for this Wednesday’s meeting.
If you could help next week with the summary, please reach out to core team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. @marybaum

#6-0, #agenda, #dev-chat

WordPress 6.0 Release Candidate 4 (RC4) Now Available for Testing

WordPress 6.0 is scheduled for release next week on May 24, 2022! This RC4 release is the last milestone for testing ahead of the official release.

You can view changes since the RC3 release via Gutenberg and Trac.

Thank you to all of the contributors who tested the 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). releases and provided feedback. Testing is a critical part of making each release strong and a great way to contribute to WordPress.

Installing RC4

This version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on production or mission-critical websites. Instead, it is recommended that you install RC4 on a test server and site. 

You can test WordPress 6.0 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 “Beta/RC Only” stream).

Option 2: Direct download the release candidate version (zip).

Option 3: Run the following command to upgrade via 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/:
wp core update --version=6.0-RC4

Plugin and Theme Developers

All plugin and theme developers are encouraged to complete testing of their respective extensions against WordPress 6.0 RC4 and update the “Tested up to” version in their readme file to 6.0 this week. If you find compatibility problems, please post detailed information to the support forums, so these items can be investigated promptly.

Review the WordPress 6.0 Field Guide, for more details on this release.

You can find additional information on the entire 6.0 release cycle.

Check the Make WordPress Core blog for 6.0-related developer notes for further details on the 6.0 release.

How to Help Test WordPress

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to 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 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. This is also where you can find a list of known bugs.

Can you speak and write in a language other than English? Help translate WordPress into more than 100 languages!


A Haiku for RC4

R-C-4 just shipped
Are you ready for six-oh?
Help us test once more


Thank you to the following contributors for collaborating on this post: @dansoschin, @webcommsat.

#6-0, #releases