WordPress 5.7.1 RC 1

WordPress 5.7.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!

Here are two ways to test WordPress 5.7.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 (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. nightlies option)
  • Download the release candidate here (zip)

What’s in this release candidate?

5.7.1 Release Candidate 1 features 23 bug fixes on CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., as well as 8 bug 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.

Fixed Core tickets from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.:

  • #52787 – Empty array for non-single 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. breaks post save through 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/.
  • #52822 – PHPMailer change in WordPress 5.7 breaks working sites
  • #52670Adminadmin (and super admin) pointer arrow border color darker than pointer content
  • #52713 – Reverse logic in wp_robots function and 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.
  • #52743 – Hardcoded SVG image URLs on WP 5.7 About screen
  • #52750 – WP 5.7 colors inconsistent in get_option( 'admin_color' ) since color contrast changes
  • #52751UIUI User interface issue on Privacy Policy Guide page
  • #52756 – Duplicate video URLs on WP 5.7 About screen
  • #52758 – 5.7 About Page: Image comparison doesn’t work on first load on some browsers
  • #52760 – Color not 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) for AA
  • #52764 – Classic editor adding empty tags in some media embed situations
  • #52768 – WordPress post URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org oEmbed rendering blocked by iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. lazy-loading
  • #52783 – Health Check mis-reports httpsHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. functionality in certain situations
  • #52789 – Gallery layout block adds all media items when changing an image
  • #52816 – Post metaboxMetabox A post metabox is a draggable box shown on the post editing screen. Its purpose is to allow the user to select or enter information in addition to the main post content. This information should be related to the post in some way. style Twenty Seventeen has a border
  • #52826 – New wp_getimagesize() causing unexpected failures
  • #52834 – Reset password screen: improve buttons layout for better 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.
  • #52891 – Privacy: print screen reader text message
  • #52894 – The wp_sanitize_script_attributes function added in version 5.7 does not escape attributes in some cases
  • #52932 – Rest Api enum validation does not work correctly WordPress 5.7
  • #52961 – Add ‘object-position’ as an allowed CSSCSS Cascading Style Sheets. attribute
  • #52981 – Twenty Twenty-One: Update IE specific editor stylesheet

Fixed Block editor issues from 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/:

  • PR30218 – Core Data: Use getAuthors for showCombobox
  • PR30524 – Editor: Revert (#27717) save editors value on change
  • PR30122 – Gallery: Set addToGallery prop to false when images don’t have IDs
  • PR29809 – Revert: Show empty paragraphs on fronted
  • PR29860 – Try: Fix gallery item clicking
  • PR29920 – Fix sibling block inserter displaying at end of block list
  • PR30125 – Block Editor: Ensure that uncategorized block types are properly handled
  • PR30243 – Add object-position to allowed inline style attributes list

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 any changes to the 5.7 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 5.7.1 schedule, the final release is expected on Wednesday April 14, 2021 around 23:00 UTC. Please note that this date/time can change depending on possible issues after RC1 is released.

The 5.7.1 release is being lead by @peterwilsoncc and @audrasjb.

#5-7, #5-7-1, #minor-releases, #releases

A Week in Core – April 5, 2021

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 March 29 and April 5, 2021.

  • 25 commits
  • 26 contributors
  • 41 tickets created
  • 5 tickets reopened
  • 34 tickets closed

Reminder: WordPress 5.7.1 is planned for April 14, 2021, so we are currently in the development cycle of the next 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..

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.

Code changes

Build/Test Tools

  • Rename some Grunt tasks to use hyphens instead of camelCase – #52625
  • Fix jQuery deprecation – #51812
  • Cleanup link-manager.zip after 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/. tests are finished – #52579
  • Prevent the workflow for testing old branches from running on forks – #52653

Coding Standards

  • Give some variables in WP_Importer a more meaningful name – #52627
  • Use strict comparison in wp-admin/includes/class-wp-filesystem-*.php#52627
  • Move some translator comments to the correct place – #52627
  • Remove some extra whitespace in get_item_schema#52627
  • Removing unnecessary parentheses from require_once in wp-admin/options-privacy.php#52627
  • Use strict comparison in wp-admin/includes/class-core-upgrader.php#52627
  • Remove some extra whitespace in _wp_translate_postdata()#52627

Documentation

  • Clarify return results for a non-existing ID in metadata functions – #51797
  • Document the import_id parameter of wp_insert_post()#52943
  • Add documentation for the ::setup_export_contents_test method used in personal data export tests – #51423
  • Fix indentation for wp_term_query->construct method parameters – #52839

Editor

  • Update the default writing prompt to match 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 – #52948
  • Consolidate enqueueing block editor assets in wp-includes/default-filters.php#52920
  • Enqueue assets for format library for the block editor – #52920

External Libraries

  • Update Underscore to version 1.12.1 – #45785
  • Upgrade PHPMailer from 6.3.0 to 6.4.0 – #52822
  • Update polyfill versions in the script loader – #52854
  • Update the path to polyfill-library files in Webpack – #52854
  • Update several polyfill libraries – #52854

Formatting

  • KSES: Add object-position to the list of safe CSSCSS Cascading Style Sheets. properties – #52961

REST API

  • REST API: Correct enum validation for numeric values – #52932

Props

Thanks to the 26 people who contributed to WordPress Core on Trac last week:

@SergeyBiryukov (5), @desrosj (4), @audrasjb (3), @TimothyBlynJacobs (2), @rachelbaker (2), @gziolo (2), @yakimun (1), @Synchro (1), @hellofromTonya (1), @ellatrix (1), @donmhico (1), @ocean90 (1), @galbaras (1), @ayeshrajans (1), @tigertech (1), @Mamaduka (1), @johnbillion (1), @aristath (1), @stefanjoebstl (1), @davidkryzaniak (1), @icopydoc (1), @Joen (1), @TimoTijhof (1), @hareesh-pillai (1), @mukesh27 (1), and @whyisjake (1).

Please welcome our 3 new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. of the week ♥️
@stefanjoebstl, @davidkryzaniak, and @icopydoc.

Core committers: @sergeybiryukov (11), @davidbaumwald (7), @desrosj (4), @ocean90 (1), @jorbin (1), and @gziolo (1).

#5-7-1, #5-8, #week-in-core

Dev Chat meeting Summary – March 31, 2021

This is the weekly meetings summary of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team. The facilitator for this week’s chats was @markparnell at 05:00 UTC and @francina at 20:00 UTC. Here is the meeting agenda.

Link to 05:00 UTC devchat meeting on the core channel on Slack

Link to 20:00 UTC devchat meeting on the core channel on Slack

Announcements & News

Upcoming releases

WordPress 5.7.1

In line with the trial for consistent minor release leads for each major branch, all the 5.7.x point releases will be led by @peterwilsoncc, with @audrasjb as deputy.

Here is the expected 5.7.1 release schedule:

  • 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).: Wednesday 7 April, 2021 around 23:00 UTC
  • Final release: Wednesday 14 April, 2021 around 23:00 UTC

There are 33 tickets in the milestone:

  • 10 are already closed as fixed
  • 3 are fixed and reopened for proper 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.

@audrasjb announced a new 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. scrub right after the devchat, and will run another one on Tuesday April 6, 2021 at 20:00 UTC.

Note: At the time this meeting recap is published, there are now 31 tickets in the milestone. 12 are fixed, 4 are reopened. The ticketticket Created for both bug reports and feature development on the bug tracker. with the higher priority was fixed (#52822).

Please note that this WordPress 5.7 board is the one to watch for 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/ updates that will need to land in this release.

WordPress 5.8

@francina shared some blogposts worth reading, where a new, experimental, release cycle is proposed, and the early bug scrubs schedule is now available.

Core related blogblog (versus network, site) posts

Some thoughts were shared about the last item (Add a testing template to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.). People are invited to comment in the blog post.

@francina suggested to follow make.wordpress.org/updates as this blog has updates from Make teams + project leadership.

Component maintainers updates

Build/Test Tools (@sergeybiryukov): Work has continued on backporting recent build and test tool improvements to the older branches still receiving security updates. See ticket #52653 for more details.

Date/Time (@sergeybiryukov): No major news this week.

General (@sergeybiryukov): No major news this week.

Internationalization (@sergeybiryukov): No major news this week.

Permalinks (@sergeybiryukov): No major news this week.

Menus (@audrasjb): JB did some Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. last week.

Widgets (@audrasjb): no major news this week.

Upgrade/Install (@audrasjb / @afragen): The team is still looking for feedback concerning the feature plugin. @francina asked if it would be useful to organize a test scrub. I would be a nice idea, and @afragen answered there’s a simple way to force the rollback for testing. The Upgrade/Install team will discuss this during the next #core-auto-updates weekly meeting on Tuesday April 6, 2021 at 18:00 UTC.

Toolbar (@sabernhardt): no triage planned this week, but @sabernhardt will probably will have another session in a few weeks.

Open floor

@chanthaboune noted that there are listening hours next week with her and Matt.

@annezazu dropped in a call out to help with the latest call for testing for the Full Site Editing Outreach Experiment: FSE Program Testing 4 – Building a restaurant themed header.

@chanthaboune shared that the recent Slack outage caused some additional things to break, so if folks see things that usually work but aren’t now, please feel free to let her know.

#5-7-1, #5-8, #dev-chat, #summaries, #summary

A Week in Core – March 29, 2021

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 March 22 and March 29, 2021.

  • 27 commits
  • 41 contributors
  • 60 tickets created
  • 13 tickets reopened
  • 51 tickets closed

Reminder: WordPress 5.7.1 is planned for April 14, 2021, so we are currently in the development cycle of the next 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..

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.

Code changes

Administration

  • Use a darker gray color for various adminadmin (and super admin) UIUI User interface items – #52760

Build/Test Tools

  • Remove explicit puppeteer dependency – #52843
  • Update some devDependencies#52624
  • Run code coverage workflow when the file is updated – #52786
  • Run code coverage workflow using parallel jobs – #52923
  • Do not checkout the Importer 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 in the Code Coverage workflow – #52625
  • Fix code coverage reporting to generate report from src#52786, #51734
  • Run test workflows on old branches on a schedule – #52653
  • Disable fail-fast for the NPM testing workflow – #52625

Bundled Themes

  • Twenty Twelve: Change theme version back to 3.3#52704

Documentation

  • Spell “non-existent” in a consistent way – #52628
  • Fix description for $htmlhint argument in code editor settings – #52628

Editor

  • Add image default size to 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 settings – #52896
  • Add new theme categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. for block types – #52883

General

  • Check if the _export_data_grouped 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. is an array when generating a personal data export file – #51423
  • Correct expected data type for WP_User_Search::$page property – #51423

Login and Registration

  • Restore the “Error:” prefix for the “Unknown username” message – #52914, #52915
  • Add the “Error:” prefix to some password reset messages – #52914
  • Prevent button misalignment on login screen – #52834
  • Prevent button misalignment on password reset screen – #52834

Media

  • Conditionally pass 2nd parameter to getimagesize()#52826

Posts, Post Types

  • Remove / from non-self-closing “clear” div tags – #52878

Privacy

  • Print screen reader text for the “Copy suggested policy text…” action button – #52891
  • Privacy: Wrap text in buttons on privacy policy guide – #52751

Query

  • Consistently include a space in parentheses in WP_Meta_Query::get_sql_for_clause()#49279

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/.

  • Prevent database error when deleting meta data – #52787

Robots

  • Remove contradictory directive check in wp_robots()#52713

Script Loader

  • Escape HTML5 boolean attribute names – #52894

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.

  • Use a consistent check for the $rewrite['hierarchical'] parameter – #52882

Props

Thanks to the 41 people who contributed to WordPress Core on Trac last week:

@SergeyBiryukov (7), @sabernhardt (5), @audrasjb (5), @jrf (3), @hellofromTonya (2), @mukesh27 (2), @ryelle (2), @johnbillion (2), @dd32 (2), @xknown (2), @whyisjake (2), @Mamaduka (1), @grapplerulrich (1), @Tkama (1), @davidbaumwald (1), @flixos90 (1), @jaymanpandya (1), @Cybr (1), @paaljoachim (1), @palmiak (1), @joyously (1), @BrechtVds (1), @goaroundagain (1), @TimothyBlynJacobs (1), @sumitsingh (1), @akabarikalpesh (1), @tmatsuur (1), @hareesh-pillai (1), @kaavyaiyer (1), @jillebehm (1), @pavelvisualcomposer (1), @terriann (1), @RogerTheriault (1), @rinatkhaziev (1), @peterwilsoncc (1), @Mista-Flo (1), @hellofromtonya (1), @azaozz (1), @desrosj (1), @isabel_brison (1), and @matveb (1).

Please welcome our 5 new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. of the week ♥️
@BrechtVds, @sumitsingh, @kaavyaiyer, @jillebehm, and @pavelvisualcomposer.

Core committers: @sergeybiryukov (9), @desrosj (8), @peterwilsoncc (6), @davidbaumwald (4), @gziolo (2), and @ryelle (1).

#5-7-1, #5-8, #week-in-core

Dev Chat meeting Summary – March 24, 2021

This is the weekly meetings summary of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team. The facilitator for this week’s chats was @peterwilsoncc at 05:00 UTC and @audrasjb at 20:00 UTC. Here is the meeting agenda.

Link to 05:00 UTC devchat meeting on the core channel on Slack

Link to 20:00 UTC devchat meeting on the core channel on Slack

Announcements & News

There is also a couple items on the Make/Core blogblog (versus network, site) that require feedback:

Upcoming WordPress Releases

WordPress 5.7.1

In line with the trial for consistent minor release leads for each major branch, all the 5.7.x point releases will be led by @peterwilsoncc, with @audrasjb as deputy.

Here is the expected 5.7.1 release schedule:

  • 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).: Wednesday 7 April, 2021 around 23:00 UTC
  • Final release: Wednesday 14 April, 2021 around 23:00 UTC

For now, there are 26 tickets in the milestone.
11 of them are closed as fixed, or reopened for 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. operations.

@audrasjb plan to run a 5.7.1 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. scrub on Thursday March 25, 2021 at 22:00 UTC. Everyone is welcome to attend.

Please note that this WordPress 5.7 board is the one to watch for 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/ updates that will need to land in this release.

WordPress 5.8

@chanthaboune shared some news about WordPress 5.8: @francina started to compile the planning round up and will publish it soon. @lukecarbis, @boniu91 and @hellofromtonya also compiled an early 5.8 bug scrub schedule, and published it right after the devchat.

Component maintainers updates

General (@sergeybiryukov): Work has continued on further fixing jQuery deprecations in WordPress core. See ticketticket Created for both bug reports and feature development on the bug tracker. #51812 for more details.

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. (@sergeybiryukov): The list of translations for selecting a timezone in General Settings was updated to add two new timezones and remove some older duplicates. See ticket #52861 for more details.

Build/Test Tools (@sergeybiryukov): no major news this week.

Date/Time (@sergeybiryukov): no major news this week.

Permalinks (@sergeybiryukov): no major news this week.

Themes (@williampatton): the component has had quite a lot of eyes recently but extra help would be appreciated.

Site Health (@clorith): the component has one ticket for 5.7.1, it’s got a proposed solution and feedback. Everyone is welcome to contribute.

Upgrade/Install (@audrasjb): no major news this week.

Menus / Widgets: @audrasjb started to silently scrub both of their awaiting review tickets, in order to prepare 5.8 effort.

Toolbar (@sabernhardt): there is a Toolbar component triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. scheduled on Thursday March 25, 2021 at 15:00 UTC. Also, the Core team nominated @sabernhardt as Toolbar component maintainer and he accepted.

Open floor

@isabel_brison requested some feedback on an overview ticket for adding end-to-end tests to WordPress Core.
The ticket contains suggestions for how to test most of the pages in the WordPress dashboard but requested some feedback on how to, or whether to, test certain pages.

@francina provided a document produced by her colleagues at Yoast recently. These are now available on the ticket.​

@clorith started a discussion on more frequently merging updates from the Gutenberg 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 in to Core. Highlighting that this would make testing future releases of WordPress features easier without keeping track of which features will remain in the plugin for the time being. There was general support for the idea.​ @chanthaboune is offered her help to move this forward.

@estelaris requested assistance for the Docs team in reviewing end user documentation. Particularly some of the more technical details. Anyone wishing to offer assistance can get in touch via the #docs channel 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/. or by messaging @estelaris directly.​

@peterwilsoncc requested some highlighted the workflow report for the 5.7.1 release due in April. For contributors wishing to write code and see it released quickly, Peter recommend they review tickets on the “needs patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.” section of the report. Contributors wishing to test or review suggested code can review tickets on the “has patch/needs testing” section of the report.

@webcommsat requested people share two items with the marketing team via shared documents:

Thanks @peterwilsoncc for his help to compile the meetings notes.

#5-7-1, #5-8, #dev-chat, #summaries, #summary

A Week in Core – March 22, 2021

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 March 15 and March 22, 2021.

  • 24 commits
  • 21 contributors
  • 92 tickets created
  • 7 tickets reopened
  • 85 tickets closed

Reminder: WordPress 5.7.1 is planned for April 14, 2021, so we are currently in the development cycle of the next 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..

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.

Code changes

Administration

  • Make focus states consistent in adminadmin (and super admin) menu when collapsed – #32579

Build/Test Tools

  • Update some devDependencies#52624
  • Revert [50540]#52843
  • Remove explicit puppeteer dependency – #52843
  • Move the get_current_commenter() method next to the test it’s used in – #52625
  • Correct some newly introduced @covers tags – #39265

Coding Standards

  • Move some translator comments to the correct place – #52627
  • Add missing semicolon to some endif keywords – #52627
  • Use strict comparison for return type checks in a few functions – #52627
  • Use strict comparison in wp-admin/includes/class-wp-upgrader.php#52627
  • Add a space before / character in some self-closing HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. tags – #52870
  • Use strict comparison for JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. fragment in some admin files – #52845, #41988

Documentation

  • Fix typo in pre_term_link 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 – #52628
  • Correct formatting for the description of some register_post_type() parameters – #52836

Emoji

  • Update the Twemoji library to version 13.0.2 – #52852

External libraries

  • Update generated script loader version hashes – #52850
  • Further fix jQuery deprecations in WordPress core – #51812
  • Update the jQuery Form library – #52685
  • Update Clipboard.js library to version `2.0.8` – #52850
  • Update jQuery Color library to version `2.2.0` – #51405

Internationalization

  • Update list of continents and cities for the timezone selection – #52861
  • Remove duplicate entries from the list of continents and cities – #52861

Media

  • Pass the appropriate reference into wp_getimagesize#52826

Pointers

  • Make pointer border darker to match arrow tip – #52670

Props

Thanks to the 21 people who contributed to WordPress Core on Trac last week:

@SergeyBiryukov (2), @laxman-prajapati (1), @Bueltge (1), @audrasjb (1), @isabel_brison (1), @rnaby (1), @nayanchamp7 (1), @desrosj (1), @hareesh-pillai (1), @Clorith (1), @melchoyce (1), @afercia (1), @wangql (1), @johnjamesjacoby (1), @whyisjake (1), @rinatkhaziev (1), @hellofromTonya (1), @Mista-Flo (1), @terriann (1), @mukesh27 (1), and @jrf (1).

Please join me to welcome our 2 new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. of the week ♥️
@nayanchamp7 and @wangql

Core committers: @sergeybiryukov (13), @desrosj (7), @ryelle (2), @whyisjake (1), and @peterwilsoncc (1).

#5-7-1, #5-8, #week-in-core

WordPress 5.7.1 maintenance release schedule

Since the release of WordPress 5.7 a small number of bugs have been identified will benefit from a maintenance release.

Now, it’s time to merge these changes into a new WordPress minor 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. and to address the other tickets that have appeared in the meantime.

The following release schedule is being proposed:

  • 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).: Wednesday 7 April, 2021 around 23:00 UTC
  • Final release: Wednesday 14 April, 2021 around 23:00 UTC

At the time of writing, 18 tickets have been identified for the 5.7.1 milestone and 48 tickets submitted since March 9 are awaiting review.

In line with the trial for consistent minor release leads for each major 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 release leaders for the 5.7.x releases will be:

  • Release leadRelease Lead The community member ultimately responsible for the Release.: @peterwilsoncc
  • Deputy Lead: @audrasjb

#5-7, #5-7-1