DevChat meeting Summary – April 21, 2021

@peterwilsoncc and @audrasjb led the weekly meetings of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, respectively at 05:00 UTC and 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

Release announcements

WordPress 5.7.1

WordPress 5.7.1 was released on Wednesday April 14, 2021. This security and maintenance release features 26 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. fixes in addition to two security fixes.

There are only 6 tickets in the next milestone (5.7.2), and as for now there is no urgent thing to address.

WordPress 5.8

Some blogblog (versus network, site) posts were published on Make/Core:

@annezazu shared that 2 weeks are left to go on a Query Quest and give feedback. Worth noting there is also an Italian version of the testing process (props to @piermario). If you have issues with the call for testing or questions about setting up a test site, please feel free to ask @annezazu in the #fse-outreach-experiment channel on 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/..

@chanthaboune shared that the next step for WP 5.8 is to get a release team together.

While she’s finally not available to lead the release squad, @francina will be available to help wrangling contributors and mentoring. She will also publish a call for release team members on Make/Core.

Make/Core News

Blog posts that need feedback: FLoC concerns

One blogpost was discussed during most of the meeting time:

@carike posted the proposal, and an active discussion started with more than 100 commenters. For those interested, there is a summary of the discussion on WP Tavern. Worth also noting that @helen, lead developer of the project, published a top comment about the proposal.

@peterwilsoncc previously shared a comment from the Security team in the initial post: based on the information presented, this should not be considered a security issuesecurity issue A security issue is a type of bug that can affect the security of WordPress installations. Specifically, it is a report of a bug that you have found in the WordPress core code, and that you have determined can be used to gain some level of access to a site running WordPress that you should not have. at this time.

Worth noting that 3 people from Google Chrome DevRel team attended the meeting: @michaelkleber as Chrome Tech Lead for the ads-related APIs, @r0wan and @samdutton as Chrome DevRel.

Below you’ll find some direct quotes from this open floor discussion:

@michaelkleber shared that the FLoC initiative is just at the beginning of what Chrome calls an Origin Trial — that’s the way we introduce new proposed APIs to get feedback from developers.

@joyously asked whether FLoC simply is a cookie of another flavor or not.
@r0wan answered there is a key difference with a cookie is that it’s a 1:1 token the server sets on the client. With the FLoC id, it’s a 1:many grouping that does not enable that same direct link back to an individual across different sites. It’s also not a value that the server gets to set for the client.
@michaelkleber added that the key contrast with third-party cookies is that a FLoC cohort can’t be used to know information specifically about you. Instead it allows some kind of probabilistic information about a large group of people that you’re temporarily part of (each FLoC cohort has thousands of people in it).

@carike shared with a detailed use case and asked for the safeguards that are in place to prevent this.

@helen’s asked what is the utility is of disabling FLoC on the content provider front vs. on the consumer front.
@michaelkleber answered that in the final end state, they expect the way FLoC will work is that the only pages that will be relevant to calculating your cohort are the pages that call the FLoC 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..  So pages will “opt in” by using some new JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. function call. The 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. headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. being discussed here was introduced as a way that pages could include random 3rd-party JS without worrying that it would invoke that API without them expecting it. So the HTTP header is saying “There is a new API that exists in the web, and I want to be sure my page cannot use it”.

@michaelkleber: FLoC doesn’t involve saving any new information, it’s just calculated based on the recent browsing history — and not the full URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org even, just the domain name.

@helen: So on its own by default, a WordPress-served page of content is not going to be used to calculate. However, if you were to, say, embed something that includes a piece of JS, that JS could then call the API and it would include the entire page?
@r0wan answered: so a default WordPress page with no use of the FLoC JS API and no ad-tagged resources in it will not be used as part of the FLoC calculations. If that site includes a third-party that uses FLoC then that would include the top-level page.

@michaelkleber: There is a bunch of on-device clustering that goes into making sure that your FLoC is shared with thousands of other people. If you want to read more about the technical details of clustering, here’s the page that describes it all.

@macmanx: So, is there’s no point in a site blocking FLoC if that site is not using FLoC-enabled resources? If a site were not using AdSense, it’s most likely not even going to be included in FLoC? And, on the other hand, if that site were already running AdSense, it probably benefits from FLoC and would not want 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.?

@samdutton nodded: During the current FLoC origin trial, a page visit will only be included in the browser’s FLoC computation for one of two reasons:

@macmanx: So, FLoC only triggers when resources that benefit (or are assumed to benefit) from FLoC are present. If I have that right, then WordPress blocking FLoC software-wide would be similar to blocking Google Fonts software-wide. It would have an effect but would actually be more of a negative impact to the site itself.

@michaelkleber: We’re running the Origin Trial so that we can get feedback, and what we hear from people (including you, now) is the kind of feedback that affects the end decision.
So it seems to me that this group is generally in favor of our best-guess plan (only look at pages that actually invoke the FLoC API), for which thank you. But I’m sure we’ll hear other opinions as well.

@mkaz: I think debating the merits of FLoC is a bit beyond the point, it may or may not be evil, probably no more or less than say AdSense. Where we wouldn’t introduce something to WordPress that would explicitly block a site from implementing AdSense, right?
@carike: The proposal just changes it from opt-out to opt-in. It does not prohibit someone from opting in.
@westonruter: If the page has to opt-in to FLoC by using an API then what’s the point of also requiring the site to opt-in to allowing FLoC as well? Going back to the Google Fonts example, if WordPress blocked Google Fonts from being used except if an opt-in is used, then if a theme enqueued a Google Font stylesheet then they’d also have to add the code to opt-in to not blocking Google Fonts. That doesn’t make sense to me. It’s like requiring a double opt-in?
@mkaz: It doesn’t seem like the area of the WordPress software to automatically opt people out of something in their browser.

@helen: So, a user/consumer disabling FLoC in their browser would mean they are not dropped into a bucket that’s used to determine ads/whatever that they see around the web (or… wherever). A WordPress site by default will not be used as a part of determining a given user’s bucket.
@macmanx: It seems to me, based on all this discussion, the best place for anti-FLoC measures are in the browser under control of the viewer, not in the site. If a site is triggering FLoC in the first place, it likely intends to benefit from FLoC in some way.

@carike shared a quote from the Chromium repository: “Any request made within an ad 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. is considered an ad resource request.”
@michaelkleber: The point is that Chrome’s Ad Tagging is trying to figure out exactly which resources are ads — very important if you want to, for example, unload ads that use too many bytes.  So the rule is “anything loaded inside an ad counts as part of the ad”. But for FLoC, we’re asking a much coarser question: “Does this page have any ad stuff on it at all?”  So details about which specific items are part of that ad are irrelevant.

@jorbin: In my personal opinion, WordPress is best off making a decision of no action at this time (not that we are making a decision in the meeting). FLoC as of right now is in such a small trial that we as a project should continue to monitor it and try to encourage that the final implementation is one that is going to align with us a project, but as of now it doesn’t present any danger to individuals on the web and in fact has the potential to benefit many publishers.

At the end of the chat, @jorbin shared a reminder about the Post & Comment Guidelines on Make/Core blogs to everyone that has posting abilities on make/core that we do have a page with expectations for posting there and that 1) All posts should be peer reviewed (it currently states by 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., but I personally would say project leaders who are not committer would fall into that bucket) and 2) That the peer reviewer should be recognized in the post.

The Google Chrome DevRel Team members shared that everyone is welcome to get in touch them via the chromiumDev Twitter account or the FLoC repository on GitHub.

After the devchat, @helen opened a ticketticket Created for both bug reports and feature development on the bug tracker. to summarize the discussion and to discuss the next steps: #53069: Consider implications of FLoC and any actions to be taken on the provider (WordPress) front. Everyone is welcome to contribute to the discussion in this Trac ticket.

Thanks @chanthaboune for the quick review.

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

Dev Chat Agenda for April 21, 2021

Here is the agenda for this week’s meetings to occur at the following times: April 21, 2021 at 5:00 UTC and April 21 2021 at 20:00 UTC.

Release Announcements

Blogblog (versus network, site) Post Highlights

Blog posts that need feedback

Components check-in and status updates

  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to our standard list above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you, accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-7-1, #5-8, #agenda, #dev-chat

A Week in Core – April 19, 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 April 12 and April 19, 2021.

  • 26 commits
  • 22 contributors
  • 44 tickets created
  • 5 tickets reopened
  • 37 tickets closed

WordPress 5.7.1 was released on April 14, 2021.

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

  • Make adjustments to how often old branches are tested – #52653

Bundled Themes

  • Bump versions for WordPress 5.7.1 – #52859

Coding Standards

  • Use strict comparison in wp-admin/includes/class-wp-media-list-table.php#52627
  • Fix WPCSWordPress Coding Standards A collection of PHP_CodeSniffer rules (sniffs) to validate code developed for WordPress. It ensures code quality and adherence to coding conventions, especially the official standards for WordPress Core. issues in wp-admin/includes/class-wp-comments-list-table.php#52627
  • Use strict comparison in wp-admin/includes/class-walker-nav-menu-edit.php#52627
  • Give a variable in WP_Automatic_Updater::after_core_update() a more meaningful name – #52627
  • Use strict comparison in wp-admin/includes/class-custom-image-header.php#52627
  • Use strict comparison in wp-admin/includes/class-custom-background.php#52627
  • Rewrite a fragment in request_filesystem_credentials() for clarity and to avoid repetition – #52627
  • Use strict comparison in wp-admin/includes/file.php#52627
  • Use strict comparison in wp-admin/includes/class-wp-automatic-updater.php#52627

Documentation

  • Correct comment format in `wp-adminadmin (and super admin)/edit-tags.php`, remove extra space – #46428

Editor

  • Update WordPress packages to use with WordPress 5.8 – #52991
  • 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. changes for WordPress packages added in 5.7.1 – #52912
  • Blocks: Add is_default handling to server side 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. styles registry – #53006

External libraries

  • Include upstream GetID3 fix for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8

Feeds

  • Rename “Summary” to “ExcerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox.” in Reading Settings – #52987

Internationalization

  • Add context to strings when updating a 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 or theme with a ZIP package – #53017, #52625

Privacy

  • Ensure “Export Personal Data” does not generate invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML.#52892

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

  • Allow authors to read their own password protected posts

Site Health

  • Remove Ajax requests from dashboard widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user.#49814
  • Correct array key for the default tab – #47225
  • Support custom sub-menus and pages – #47225
  • Correct test result status for the 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. test – #52783

Upgrade/Install

  • Correct the alignment of error messages for the language installer – #52989

Props

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

@SergeyBiryukov (3), @mukesh27 (3), @peterwilsoncc (3), @jrf (2), @xknown (2), @xavivars (1), @dimadin (1), @desrosj (1), @TimothyBlynJacobs (1), @audrasjb (1), @sabernhardt (1), @immeet94 (1), @hellofromTonya (1), @arena (1), @timothyblynjacobs (1), @swissspidy (1), @zieladam (1), @andraganescu (1), @aristath (1), @youknowriad (1), @ramiy (1), and @ravipatel (1).

Core committers: @sergeybiryukov (11), @desrosj (4), @clorith (3), @gziolo (3), @davidbaumwald (3), @peterwilsoncc (1), and @ocean90 (1).

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

DevChat meeting Summary – April 14, 2021

@markparnell and @audrasjb led the weekly meetings of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, respectively at 05:00 UTC and 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

Upcoming WordPress releases

WordPress 5.7.1

Since no issue was raised after the release candidate, WordPress 5.7.1 was released a few hours after the devchat. It contains 26 bugfixes and 2 security fixes.

WordPress 5.8

Some blogblog (versus network, site) posts were published on Make/Core:

While it happened after the meeting, it’s important to note that the Full Site Editing Go/No Go decision was published on April 14, 2021.

@annezazu mentioned the latest call for testing for the FSE Outreach Program. This week, it’s about the Query Block.

Announcements and news

Please note that these posts are still waiting for feeback:

Component maintainers updates

General (@sergeybiryukov): Sergey has started chipping away at some long-standing coding standards issues in core, see ticketticket Created for both bug reports and feature development on the bug tracker. #52627 for more details.

Build/Test Tools, Date/Time, Internationalization, Permalinks (@sergeybiryukov): No major news this week.

Site Health (@clorith): No major news this week.

Menus, Widgets and Upgrade/Install (@audrasjb): No major new this week.

@audrasjb mentioned there are still many Core components looking for new maintainers:

  • Cache 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.
  • Database
  • Help/About (@marybaum)
  • Quick/Bulk Edit
  • Feeds
  • Filesystem API
  • Import
  • Mail
  • Plugins
  • Post, Post types
  • Login and registration

@marybaum volunteered to maintain the Help/About component. This request was accepted by the Core team.

Open floor

@webcommsat shared that lots of people have been asking about WCEU dates (7-10 June 2021). The community team is looking at how they promote contributing this year too. More soon.

Ticket #53014 was mentioned in both 5:00 UTC and 20:00 UTC devchats. It’s in milestone 5.8. It wasn’t fixed in previous releases as it still needs a 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. and proper testing. 

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

Dev Chat Agenda for April 14, 2021

Here is the agenda for this week’s meetings to occur at the following times: April 14, 2021 at 5:00 UTC and April 14, 2021 at 20:00 UTC.

Release Announcements

Blogblog (versus network, site) Post Highlights

Blog posts that need feedback

Components check-in and status updates

  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to our standard list above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you, accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-7-1, #5-8, #agenda, #dev-chat

A Week in Core – April 12, 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 April 5 and April 12, 2021.

  • 26 commits
  • 42 contributors
  • 54 tickets created
  • 9 tickets reopened
  • 45 tickets closed

Reminder: WordPress 5.7.1 is planned for April 14, 2021. The release candidate is available for testing.

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

  • Update various background colors for increased contrast – #52760

Build/Test Tools

  • Remove remaining Travis CI references – #52161, #52666
  • Prevent PHPUnit tests on push for forks/private mirrors – #52983
  • Update dependencies in default themes – #52624
  • Update development dependencies from WP packages – #52991
  • Revert package-lock.json change in [50682]#52768
  • Update some dependencies – #52624

Bundled Themes

  • Update the “Tested up to” value – #52859
  • Twenty Twenty-One: Rebuild IE specific editor stylesheet – #52981, #52702

Coding Standards

  • Rewrite a fragment in request_filesystem_credentials() for clarity and to avoid repetition – #52627
  • Use strict comparison in wp-admin/includes/file.php#52627
  • Simplify the check for parent terms in export_wp()#52627
  • Use strict comparison in wp-admin/includes/credits.php#52627
  • Use strict comparison in wp-admin/includes/comment.php#52627
  • Remove unnecessary unset() calls in WP_Importer methods – #52996
  • Use strict comparison in wp-admin/includes/dashboard.php#52627
  • Give a variable in wp-admin/themes.php a more meaningful name – #52627

Customize

  • Set `playsinline` attribute for custom headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. videos – #50111

Editor

  • Use a consistent way to retrieve post ID on Edit Post screens – #52995
  • Ensure wordpress/inteface package is listed as a dependency – #52991

Login and Registration

  • Check if $_GET['login'] is set before using it in wp-login.php#52980

Media

  • Do not lazy load hidden images or embeds – #52768

Options, 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. APIs

  • Update default color scheme swatch to match CSSCSS Cascading Style Sheets. changes – #52750

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 the rest_jsonp_enabled 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. before setting the Content-Type header – #52691

Site Health

  • Reduce false reports of 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. failures – #52783

Themes

  • Remove unused code fragment from wp-admin/themes.php#53005

Props

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

@peterwilsoncc (3), @SergeyBiryukov (3), @mukesh27 (3), @johnbillion (2), @TimothyBlynJacobs (2), @ocean90 (2), @ravipatel (2), @klevyke (1), @annalamprou (1), @AnotherDave (1), @ayeshrajans (1), @bobbingwide (1), @Clorith (1), @dragongate (1), @geoffrey1963 (1), @eatsleepcode (1), @gab81 (1), @ninetyninew (1), @Ipstenu (1), @k3nsai (1), @mmuyskens (1), @nicegamer7 (1), @pwallner (1), @ryelle (1), @swissspidy (1), @desrosj (1), @melchoyce (1), @dd32 (1), @rkradadiya (1), @davidbaumwald (1), @jrf (1), @rachelbaker (1), @kebbet (1), @adamsilverstein (1), @audrasjb (1), @fabianpimminger (1), @flixos90 (1), @jonkastonka (1), @joyously (1), @SirStuey (1), @satrancali (1), and @Toru (1).

Please welcome our 17 (!!) 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 ♥️
@klevyke, @annalamprou, @AnotherDave, @dragongate, @geoffrey1963, @eatsleepcode, @gab81, @ninetyninew, @k3nsai, @mmuyskens, @nicegamer7, @pwallner, @rkradadiya, @fabianpimminger, @jonkastonka, @SirStuey, and @satrancali.

Core committers: @sergeybiryukov (11), @desrosj (5), @peterwilsoncc (4), @ocean90 (2), @gziolo (2), @rachelbaker (1), and @ryelle (1).

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

Dev Chat meeting Summary – April 7, 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 @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 (released)
  • Final release: Wednesday 14 April, 2021 around 23:00 UTC

@audrasjb announced (and hosted) 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.

Note: At the time this meeting recap is published, WP 5.7.1 Release Candidate 1 is now available for testing.

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

@annezazu shared that the current FSE call for testing is now open for feedback until April 12th rather than April 8th. Hopefully, this gives people an extra weekend to chime in and share their experience.

@chanthaboune pointed out that the first go/no go date for FSE in WP5.8 is next Tuesday.

@nalininonstopnewsuk shared that it is possible share FSE Call for Testing on social and FSE Call for Testing on LinkedIn.

@francina shared this blog post from the Marketing Team: Thoughts on Marketing, FSE, and What’s Next. It’s relevant to the current release, so please read and leave your feedback.

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 ticketticket Created for both bug reports and feature development on the bug tracker. #52653 for more details. A post is also upcoming on make/core.

Date/Time, General, 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 (@sergeybiryukov): No major news this week.

Menus, Widgets, Upgrade/Install (@audrasjb): No major news this week.

Site Health (@clorith): The only ticket in milestone 5.7.1 was committed in time.

@francina also pointed out the ticket she opened in Meta Trac concerning Component maintainers updates. In the past month she also reached out to the majority of the components and removed inactive maintainers. Right now there are quite a lot of components without maintainers.

The attendees discussed about maintainers recruitment. If anyone is interested to help to maintain a component, @audrasjb pointed out that he would be happy to mentor/explain what he is doing on the few components he maintains. @francina proposed an online meeting/Q&A, like the casual online gatherings hosted by the community team.

Open floor

@paaljoachim asked what is the definition of what can and not not be included in a 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..

@jeffpaul quoted the Core team handbook: “A minor release is intended for bugfixes and enhancements that do not add new deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. files and are at the discretion of the release leadRelease Lead The community member ultimately responsible for the Release. with suggestions/input from component maintainers and committers.”

@sergeybiryukov added that generally, minor releases are addressing regressions introduced in the latest release and some follow-up changes to new features, with occasional fixes for bugs from other recent releases, and occasional enhancements that the release leads feel are necessary.

#5-7-1, #5-8, #core-auto-updates, #dev-chat, #summary

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

Dev Chat Agenda for April 7, 2021

Here is the agenda for this week’s meetings to occur at the following times: April 7, 2021 at 5:00 UTC and April 7, 2021 at 20:00 UTC.

Announcements

Blogblog (versus network, site) Post Highlights

Blog posts that need feedback

Components check-in and status updates

  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to our standard list above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you, accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-7-1, #5-8, #agenda, #dev-chat

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