Bethany Chobanian Lang 6:33 pm on January 18, 2022
Tags: , , ,   

Performance team meeting summary 18 January 2022

Meeting agenda here and the full chat log is available beginning here on Slack.

Focus group updates

Announcements

@shetheliving

  • Introducing updated GitHub repo labels
    • The labels beginning with “Needs” all need something from the community: discussion, decision (see below), development, code review, and/or testing
    • Issues labeled Needs Decision will have a comment noting a proposed next step and a request for vote via thumbs-up/thumbs-down emoji, as well as a deadline for voting. We’ll allow at least two weeks for voting and will flag these issues in our weekly chat.

Images

@adamsilverstein

GitHub project

  • We’re seeking an additional POC for this group; if you’re interested, please comment here or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” 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/.
  • Requesting additional feedback on https://github.com/WordPress/performance/issues/96 (note that this was previously a discussion: https://github.com/WordPress/performance/discussions/83)
    • @mitogh: One option is to extend sizes array to include a new property called sources with the MIME type as the key of that array and a path to the original file to create a picture element
    • @flixos90: The picture element adds a layer of complexity in terms of adding to WP coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.; not sure it’s necessary for us to introduce WebP support.
    • @pbearne: Would be nice to control the quality of images for each size (@adamsilverstein: see https://core.trac.wordpress.org/ticket/54648)
      • @schlessera: WebP is not ready to replace JPEG at this point
    • @dainemawer: What about AVIF?
      • @flixos90: The picture element would be a clear requirement for AVIF, since it has too little browser support
    • Several people chimed in on a discussion regarding giving options for using WebP; see this Slack thread

Feedback requested

Object caching

@tillkruess @dustinrue

GitHub project

  • @spacedmonkey: Several core PRs (with associated issues in the Performance repo) ready for review – see below.
  • @tillkruess: Will start pushing some modules that he’s been working on. Most object caching tasks will require core commits.

Feedback requested

Site Health

@audrasjb

GitHub project

  • We’re seeking an additional POC for this group; if you’re interested, please comment here or ping in Slack
  • @dainemawer will see how he can help here

Feedback requested

  • N/A

Measurement

@wp-source @josephscott

GitHub project

  • @wp-source offline until end of January
  • @josephscott: Some challenges with getting things going on platform.sh because the WordPress 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/ repos are mirrors of the subversion repository, and configuration files should not be incorporated into the main mirrors. See this Slack thread for more details.

Feedback requested

  • N/A

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/.

@aristath @gziolo @sergiomdgomes

GitHub project

  • @sergiomdgomes: Concluded in a recent meeting that the work being explored in https://github.com/WordPress/gutenberg/issues/36716 is a blocker for most JS-based Performance work because the current enqueue mechanism precludes many potential optimizations; exploring alternatives.

Feedback requested

  • Share feedback on possible approach outlined in https://github.com/WordPress/gutenberg/issues/36716

Infrastructure

  • @flixos90: Should we open an issue to finalize the first release?
    • @justinahinon: We should wait to release until after release of 5.9 and completion of Site Health module
    • @flixos90: Will open an issue for discussion, then decision

Feedback requested

Open floor

  • N/A

Help wanted

#core-media, #performance, #performance-chat, #summary

David Smith 9:46 am on January 18, 2022
Tags: , , ,   

Editor Chat Agenda: 18th January 2022

Facilitator and notetaker: @get_dave.

This is the agenda for the weekly editor chat scheduled for 2022-01-19 14:00 UTC.

This meeting is held in the #core-editor channel in the Making 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/..

  • 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/ 12.4.0.
  • WordPress 5.9 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). 3.
  • Updates based on updated scope for site editing projects:
    • Navigation 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..
    • Template editor.
    • Patterns.
    • Styling.
    • Mobile Team.
    • Components Team.
  • Task Coordination.
  • Open Floor.

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #core-editor-agenda, #meeting

Jb Audras 11:51 pm on January 17, 2022
Tags: , ,   

A Week in Core – January 17, 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 January 10 and January 17, 2022.

  • 34 commits
  • 39 contributors
  • 74 tickets created
  • 20 tickets reopened
  • 53 tickets closed

The Core team is currently working on the next major release, WordPress 5.9 🛠

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

Administration

  • Ensure an integer is used for menu priority in add_menu_page() – #54798, #48249
  • Fix an erroneous translators comment after changeset [52569] – #54798
  • Replace “Current theme” with “Active theme” in user facing strings – #54770
  • Revert [51946] – #54837, #53587
  • Update design of the Dashboard welcome panel – #54489

Build/Test Tools

  • Re-enable E2E tests for the 5.8 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". – #54749
  • Avoid duplicate queries in some WP_Query tests – #54822
  • Trac ticket number correction after changeset [52569] – #54798

Bundled Themes

  • Twenty Twenty-Two: Sync updates 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/ for 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). 2
  • Twenty Twenty-Two: Sync updates from GitHub from RC3 – #54318

Coding Standards

  • Correct alignment in get_block_editor_settings() – #54728
  • Remove an extra variable in get_author_posts_url() – #54728
  • Rename the $val variable to $site for clarity in WP_MS_Users_List_Table::column_blogs() – #54728
  • Use strict comparison in wp-admin/includes/class-wp-ms-users-list-table.php – #54728
  • Use strict comparison in wp-admin/includes/class-wp-users-list-table.php – #54728

Database

  • Add missing AS after INNER JOIN in some queries – #54769

Docs

  • Correct description for two 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. 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. functions: – #54796
  • Miscellaneous docblockdocblock (phpdoc, xref, inline docs) corrections in 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/. and Sitemaps API – #54729
  • Typo correction in WP_REST_Response class docblocks – #54823

Editor

  • Explicitly load remote 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. patterns in the block and site editor screens – #54806
  • Fix enqueueing additional styles in wp_enqueue_block_style() to print only when blocks render – #54787
  • Update some default presets in use by default themes to the new format – #54782
  • WordPress default presets aren’t loaded for all themes – #54781
  • Site Editor: Fix typo in home template translatable description – #54787
  • Update packages to include these 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 from 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/: – #54487

Help/About

  • Correction in “Managing Themes” HelpHub Docs link – #54707
  • Update the About section for 5.9 – #54270

Internationalization

  • Contextualize “light” color translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. strings – #54804

Media

  • Add a missing / in post thumbnail lazy loading regex – #54815
  • Typo correction in wp_image_maybe_exif_rotate docblock – #54816

Script Loader

  • Fix a variable typo in wp_enqueue_block_style – #54786

Upgrade/Install

  • Check if the disk_free_space() function exists before calling it – #54826, #54730
  • Typo correction in a Core_Upgrader class inline comment – #54821

XML-RPC

  • Fix typos in some XMLRPC related docblocks – #54820

Props

Thanks to the 39 people who contributed to WordPress Core on Trac last week: @audrasjb (8), @costdev (5), @kebbet (4), @SergeyBiryukov (4), @hellofromTonya (3), @richtabor (2), @Presskopp (2), @critterverse (2), @poena (2), @kjellr (2), @oandregal (2), @joedolson (2), @danieldudzic (1), @omaeyusuke (1), @sabernhardt (1), @aristath (1), @Mamaduka (1), @domainsupport (1), @scruffian (1), @kharisblank (1), @talldanwp (1), @isabel_brison (1), @desrosj (1), @versusbassz (1), @SierraTR (1), @kirtan95 (1), @johnbillion (1), @chesio (1), @mitogh (1), @noisysocks (1), @shreyasikhar26 (1), @david.binda (1), @swb1192 (1), @jrf (1), @tobifjellner (1), @ironprogrammer (1), @dhusakovic (1), @peterwilsoncc (1), and @jdy68 (1).

Congrats and welcome to our 9 new contributors of the week: @omaeyusuke, @domainsupport, @versusbassz, @SierraTR, @kirtan95, @shreyasikhar26, @swb1192, @ironprogrammer, @dhusakovic ♥️

Core committers: @audrasjb (12), @sergeybiryukov (9), @hellofromtonya (4), @jffng (2), @ryelle (2), @davidbaumwald (2), @jorgefilipecosta (2), and @noisysocks (1).

#5-9, #core, #week-in-core

Jorge Costa 2:03 pm on January 17, 2022
Tags: , , , ,   

Editor chat summary: Wednesday, 12 January 2022

This post summarizes the weekly editor chat meeting on Wednesday, 12 January 2022, 14:00 UTC held in Slack.

WordPress and 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/ Releases

@jorgefilipecosta started the chat by saying Gutenberg 12.3 was released on the 5 of January. Details related to the Gutenberg release can be read in this post. The notable features are new blocks one can use and the gap and typography support additions to the group 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..

Regarding the WordPress release, @jorgefilipecosta said the RC2 was released on 11 of January and things are going smoothly with the WordPress release. The final WordPress 5.9 version is planned for 25 of January 2022.

From the editor side on 5.9 must-have board we still have 9 to-do items and 3 items are in progress.

Project updates

Native mobile app

Shipped

  • ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. Native v0.66 upgrade

Fixes

  • Line-height issue on Android
  • Link picker freeze when virtual keyboard is hidden
  • Text formatting issue when backspace is used
  • Cover block 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. related to the color settings

In progress

  • Final tweaks in the GSS Font size/color implementation
  • Finalizing reliability improvements of the mobile translations pipeline

Template editor, site editor, and styles

Two PR’s were submitted (#1, #2) that implement code editing for edit site and the ability to copy the template content. These PR’s when merged will bring UI parity between the site editor and post editor.

Regarding the styles project the focus was on testing things and improving what we have in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. by fixing some bugs, improving the escaping of some parts, and fixing missed backports.

Task coordination

@mamaduka

@jorgefilipecosta

Worked on bringing parity between site editor and post editor. For the next week plans on:

Open floor

WordPress 6.0 project board

@paaljoachim shared the following:

As there are issues that are punted from WP 5.9. Will it be helpful to get a project board up as soon as possible for WP 6.0 to be sure that punted issues and other issues are handled early? Similar to how TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. has a tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) for 6.0 early tickets.

@jorgefilipecosta answered that we don’t have a board for 6.0 because the assumption is everything that is being worked on will be part of 6.0.

Block editor dependency on user endpoints

@tomjn shared the following:

I had hoped to raise a subject I wanted to talk about last week but I will not be around tomorrow. I’d much appreciate anybody who can look into the issue of the editor making the 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. assumption that the user is always logged in and always has a usable active session.

This has crippled Frontenberg but also doesn’t account for expired WP sessions, cancelled sessions, etc, and does not have an appropriate fallback ( it results in a partial code editor view ). Default behaviour in WordPress has always been to show a modal dialog with the login window, and past Gutenberg behaviour has been to assume the user cannot publish and adjust the UIUI User interface accordingly e.g. submit for review rather than publish/update. It’s also prior precedent that these types of REST request are bundled with the initial page load to avoid the additional request so there are performance consequences

– https://make.wordpress.org/core/2022/01/04/editor-chat-agenda-5-january-2021/#comment-42271

– https://github.com/WordPress/gutenberg/issues/37682

@jorgefilipecosta said this seems like an issue we should address. We just need someone to work on the fix.

@tomjn said that his hunch at the moment is that getEntityRecords handles this and the same pattern would work for getCurrentUser but it’s mainly speculation. If that’s the case the fix is simple.

Typography settings consitency and list block class

@luminuu shared the following:

While testing the 5.9 RC1, I came across the inconsistency of the font family selection at the typography settings. It was reverted from the paragraph block but it is still in use in some other blocks. To avoid confusion with users, I suggested to remove the font family setting from the other blocks as well. Please have a look and share your thoughts: https://github.com/WordPress/gutenberg/issues/37826

I also want to request some help with the PR https://github.com/WordPress/gutenberg/pull/36676 as I’m struggling to have the checks running through properly. This PR is related to an issue of the 5.9 Must Have project: https://github.com/WordPress/gutenberg/issues/37388

@jorgefilipecosta said that regarding #37826 @ntsekouras created a PR to address it. Regarding #36676 the addition of a class to the list block was discussed as part of the fix to the issue #37388. @oandregal proposed an alternative fix and left his thoughts after the chat in this comment.

Unexpected style warnings

@joostdevalk shared the following:

Hey team! I have a problem I want to submit to you all.

  • In this PR an error was introduced that is thrown when Gutenberg thinks styles are not added properly.
  • As becomes clear from the content of the errors, only styles added by blocks or themes are taken into account. However, plugins can add styles as well. At Yoast we add a style sheet to add styling to our 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..
  • We haven’t changed the way we include those styles in years, but suddenly console errors started showing up. Even though nothing breaks functionally, errors are thrown, which means people will start blaming us if something actually breaks.
  • In this PR the level of the errors was lowered to warnings.
  • In October, Ella drafted a PR that would make sure no warnings were thrown anymore.
  • Because this was quite a big PR, it was decided to extract the fix related to the warnings to a separate PR. This PR has been open since about a month.
  • Earlier this week, the PR was removed from the WordPress 5.9 Must-Haves project board.

We’d really like to have Ella’s PR merged into 5.9 to prevent warnings from being thrown, to prevent support load and getting the blame for broken things that are unrelated to us.

@mamaduka said:

I’m a little worried about including the fix in 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). that hasn’t been well tested.Maybe we should remove the warning from 5.9; since plugins that add CSSCSS Cascading Style Sheets. files to the editor have no way to fix it. And as @joostdevalk mentioned, it will just increase support overhead.Then we can try and ship #37466 in 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..

@aristath added:

At this point, the warning does more harm than good. The intention behind it is good, but if we can’t fix the current implementation for 5.9, then temporarily removing these warnings makes sense

@jorgefilipecosta we can have a PR disabling the warnings and discuss in more detail on the PR.

Escaping in bocks

@fabiankaegy said the following:

I just quickly wanted to throw in this discussion I opened regarding how block should handle late escaping the content of inner blocks in dynamic blocks here: https://github.com/WordPress/gutenberg/discussions/37823It is something that keeps popping up in for example WordPress VIP code reviews and there isn’t really any guidance in the docs or in the core codebase.

@jorgefilipecosta shared that applying wp_kses_post to the content like wp_kses_post( $content ) does not seem like a good idea as a block may legitimately need to output unsafe content like javascriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. events etc and if those come from the block they are expected and safe.

@jorgefilipecosta added that the issues arise when a block outputs any information the user can manipulate like attributes. Any kind of output containing use information should be escaped as close to the output as possible. Following the WordPress principle of sanitizing sooner escaping late. @jorgefilipecosta ended the subject by sharing that @getdave is making some improvements to how core escapes information.

#block-editor, #chats, #core-editor, #core-editor-summary, #gutenberg

Bethany Chobanian Lang 1:13 pm on January 17, 2022
Tags: , , ,   

Performance Chat Agenda: 18 January 2022

Here is the agenda for this week’s performance team meeting scheduled for January 18, 2022, at 16:00 UTC.

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

#agenda, #meeting, #performance, #performance-chat

Estela Rueda 1:12 am on January 13, 2022
Tags: , , ,   

Dev chat summary: January 12, 2022

@webcommsat and @marybaum led the meeting on this agenda.

See the real-time chat in the Make WordPress Slack.

And last week’s notes are at Dev chat summary, January 5, 2021.

Announcements

WordPress 5.9 Release Candidate 2 has landed. Please download and test! Also, please feel free to share the package and invite your friends to test the 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). for themselves.

Help test WordPress 5.9 features. You can test in general or find prompts for daily features to test in  #fse-outreach-experiment.

Also, share the details of the new features with your teams and networks – Read the latest Developer Notes

@nalininonstopnewsuk asked about testing deadlines and current focuses from a question from the marketing meeting. @hellofromtonya: Testing and feedback can be ongoing. But for regressions or bugfixes to land in the final release, these would need to be reported, fixed, and committed 24 hours before the final release, which is on 25 January 2022.

Blogblog (versus network, site) posts to note

A year in core (December 29, 2021)

What’s new in Gutenberg 12.3 release (5 January 2022)

A Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.: January 10, 2022

A reminder of the revised 5.9 release schedule.

Join the discussion on 2022 release planning (December 27, 2021 post by @chanthaboune). This is still open for discussion. No current closing date.

Proposal: Approving custom block pattern directory submissions (posted January 4, feedback by January 14, 2022)
Proposed changes to javascript coding standards for full prettier compatibility 

The 5.9 Field Guide brings together the developer notes about every change in the new release. It’s a must-read if you build themes or plugins!

Update on 5.9 release

@hellofromtonya:

First of all, thank you to everyone who has contributed to the 5.9 release.

The final release is in less than 13 days on 25 January and it is on track to release on that day. There are currently no blockers or red flags. Everyone has come together across Core and 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/ to make the revised schedule happen on time as promised.

Release Candidate (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).) 2 landed yesterday and is available for testing and feedback. Please, test test test test. Regressions and bugs introduced in the RC cycle are priority to find and fix before the final release. Your help is needed to test and report. 

When is the next release? Release Candidate 3 will be on 18 January 2022. You are all invited to join and actively participate in the release party.

As a reminder, 5.9 is in a hard string freeze. Any string changes must be critically necessary — and nearly unanimously agreed as such before they show up in the 5.9 package. Why? Translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. teams are working hard translating the release and in many cases, translations are done. String changes impact not only the translators but users. Please cautiously recommend string changes only where it’s critically necessary.

One more reminder, with 5.9 in RC, code changes require two core committers: one to review and approve the 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. to 5.9 and the second to do the review and actual backport commit. Why? This is on purpose to make sure code changes are necessary and respect the release processes. With all that said, 5.9 is less than two weeks from full final release.

Additional updates

Last week, a security update, 5.8.3, arrived. @audrasjb also confirmed that updates dropped for older versions, from 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". 3.7 to 5.8, to 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. the same issues.

Component Maintainers update

Until 5.9 final release on January 25, the team is skipping component updates unrelated to 5.9. If any maintainer has something to add, please add it to the comments.

Open Floor

The core team is looking for notetakers. The idea is to create a pool and encourage more contributors, and spread the responsibility around.
@webcommsat: at and after last week’s meeting, there was a discussion about the usefulness of an advance rota for people to volunteer to write summaries for dev chat.

Writing notes is a great way to review what is happening — and learn more about items you might be interested in. Some other teams find it easier to have a rota running a couple of weeks in advance, where people can volunteer in advance rather than just asking on the day.

And when you volunteer, you are not going it alone. There’s lots of help, you can ask questions just about anytime, and at least one other person will review and help with edits too.

Finally, the summaries are really helpful for people who cannot join the live meeting or are in different timezones, but who still want to be part of what’s happening in core. So it’s a really important task. It’s a great way to get involved and contribute!

Volunteers invited for notes on:
12 Jan – Estela
19 Jan –
26 Jan –
2 Feb –
9 Feb –

@davidbaumwald: Yeah, sometimes not everyone can make the meeting, so it’s tough to find volunteers. … One perk of writing notes: You get to become an author on Make WordPress/Core.

@estelaris commented that it is a great way of meeting the team that is actually building WordPress and learn from them. @webcommsat mentioned about creating a schedule and asked anyone who would like to take notes during dev chat to post in the #core channel or comment on this summary.

There is a call for volunteers on the marketing and training teams to support 5.9, specifically in the next two weeks. You can reach out to them in their 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/. channels.

Next meeting

Dev Chat will take place next week, Wednesday 19 January 2022 at 20:00 UTC in the Make WordPress Core Slack.

Props: Dev Chat summary by @estelaris and @webcommsat. Thanks to @marybaum for proofing.

#5-9, #dev-chat, #summary

#dev-chat, #summary, #week-in-core

marybaum 7:21 pm on January 12, 2022
Tags: , ,   

Dev Chat agenda for January 12, 2021

The weekly developers chat meeting is at 20:00 UTC in the #core channel on Slack. Please join the group!

Announcements

WordPress 5.9 Release Candidate 2 has landed.  Please download and test! Also, please feel free to share the package and invite your friends to test the 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). for themselves.

Help test WordPress 5.9 features

Read the latest Developer Notes

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

A year in core (December 29, 2021)

What’s new in Gutenberg 12.2 release (5 January 2022)

A Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.: January 10, 2022

The revised 5.9 release schedule.

Join the discussion on 2022 release planning (December 27, 2021 post by @chanthaboune)

Proposal: Approving custom block pattern directory submissions (posted January 4, feedback by January 14, 2022)

Proposed changes to javascript coding standards for full prettier compatibility [added during devchat]

Do you have other posts that should get attention? Please add them in the comments.

4. Upcoming releases

@hellofromtonya will update the group on the 5.9 release, slated for January 25, 2022.

Component Maintainers

From now until 5.9 launch, devchat will skip a formal check-in so the group can have a longer Open Floor. If you’re a maintainer who would like to get help with a blockerblocker A bug which is so severe that it blocks a release. or share success/ collaboration, please feel free to either comment on this post or in the meeting.

Open Floor

Please add your topic to the comments below.

#agenda, #core, #dev-chat, #week-in-core

#5-9, #agenda, #dev-chat

Bethany Chobanian Lang 6:22 pm on January 11, 2022
Tags: , , , ,   

Performance team meeting summary 11 January 2022

Meeting agenda here and the full chat log is available beginning here on Slack.

Focus group updates

Images

@adamsilverstein

GitHub project

  • @adamsilverstein offline
  • @mitogh: Researching existing functionality and working on planning. Can we include https://core.trac.wordpress.org/ticket/53232 in GH as part of image performance improvements?
  • @tweetythierry: Sure, this will help us do some testing before it lands in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  • @mitogh will create a new GH issue linking back to the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker.
  • WebP module
    • Ready for testing
    • @tweetythierry: Should we remove the original image or not?
    • @boogah: Can we give the option? Keep the original and add a 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. to remove the original for users/hosts who wish to do so
    • @tillkruess, @madpixels, @craigfrancis: Keep the original
    • @blogaid: This will double disk space usage and we need to keep hosting costs in mind
    • @schlessera: webp is not supported everywhere, so we shouldn’t be removing the original
    • Several other users chimed in; see Slack
    • Continue the discussion 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/ (see below)

Feedback requested

Object caching

@tillkruess

GitHub project

  • No updates

Feedback requested

  • N/A

Site Health

@audrasjb

GitHub project

Feedback requested

  • Create Site Health Audit Enqueued Assets module (inc. this PR) has been adapted to the new 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 structure and is open for discussion

Measurement

@wp-source @josephscott

GitHub project

  • @wp-source offline until end of January
  • @josephscott: Plan to get a live updating test site set up on platform.sh ot begin running tests on every commit to master soon

Feedback requested

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/.

@aristath

GitHub project

Feedback requested

  • N/A

Infrastructure

Feedback requested

Open floor

  • @seedsca: Has anyone looked into using Xdebug with profiling for tests?
  • @craigfrancis: Looking for review on PR #2127 in Core since this is a feature change to wp-db

#core-media, #meeting, #performance, #performance-chat, #summary

Paal Joachim Romdahl 2:27 pm on January 11, 2022
Tags: , , ,   

Editor Chat Agenda: 12 January 2021

Facilitator and notetaker: @jorgefilipecosta

This is the agenda for the weekly editor chat scheduled for Wednesday, January 12 2021, 03:00 PM GMT+1.

This meeting is held in the #core-editor channel in the Making 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/..

  • 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/ 12.4 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).
  • What’s new in Gutenberg 12.3 ( 5 January)
  • WordPress 5.9
  • Updates based on updated scope for site editing projects:
    • Navigation 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..
    • Template editor.
    • Patterns.
    • Styling.
    • Mobile Team.
    • Components Team.
  • Task Coordination.
  • Open Floor.

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #core-editor-agenda, #meeting

Jb Audras 12:06 am on January 11, 2022
Tags: , ,   

A Week in Core – January 10, 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 January 3 and January 10, 2022.

  • 41 commits
  • 63 contributors
  • 65 tickets created
  • 8 tickets reopened
  • 51 tickets closed

The Core team is currently working on the next major release, WordPress 5.9 🛠

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

Administration

  • Add missing texture image for Welcome panel & About page – #54489, #54270
  • Refresh the Dashboard Welcome panel – #54489

Build/Test Tools

  • Add the 5.9 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". to the workflow for testing branches
  • Re-enable E2E tests for the 5.8 branch – #54749
  • Update qUnit test fixtures after [52535] – #54745

Bundled Themes

  • Fix: WordPress default presets aren’t loaded for all themes – #54781
  • Update some default presets in use by default themes to the new format – #54782
  • Twenty Twenty-Two: Sync updates 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/ for 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). 1 – #54318

Coding Standards

  • Remove empty space at end of inline comment in _add_default_theme_supports() – #54731
  • Correct alignment in get_block_editor_settings() – #54728
  • Use strict comparison in wp-admin/options.php – #53359
  • Use strict comparison in wp-admin/plugin-install.php – #54728
  • Use strict comparison in wp-admin/revision.php – #54728
  • Use strict comparison in wp-admin/themes.php – #54728

Editor

  • Update wordpress packages for WP 5.9 RC 1 – #54487

Embeds

  • Fix oEmbed host script enqueueing on 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.-based themes – #44632

External Libraries

  • Update jQuery hoverIntent to version 1.10.2 – #54722, #51812

Formatting

  • Correctly encode ASCII characters in post slugs

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

  • Improve docs for wp_remote_retrieve_header function return value – #51736

Help/About

  • Change the HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. title of Themes Screen and add related HelpHub Docs link – #54707
  • Change the Learn WP link in the about page – #54755
  • Correction in “Managing Themes” HelpHub Docs link – #54707
  • Correction on the documentation link about adding new themes – #54709
  • Use “refactoring” noun form in WordPress 5.9 About Page – #54270
  • WordPress 5.9 About Page

Login and Registration

  • Remove aria-expanded from “Generate Password” button – #54538
  • Rename login_language_switcher_args to login_language_dropdown_args – #54696
  • Rename two filters related to language dropdown for better consistency – #54696

Query

  • Improve sanitization within WP_Meta_Query
  • Improve sanitization within WP_Tax_Query

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

  • Add unit tests for the 404 template slug handler – #54680
  • Typo correction in a link description object – #54745

RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.

  • Improve _set_preview for case when autosave is missing – #54708

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.

  • Typo correction in context used for the navigation link block title – #54566

Themes

  • Make block themes support HTML5 by default – #54731, #54597

Upgrade/Install

  • Avoid using unserialize() unnecessarily
  • Fix parameter count in error call when an automatic core upgrade fails – #53284
  • Make first comment URLs translatable – #54535

Props

Thanks to the 63 people who contributed to WordPress Core on Trac last week: @hellofromTonya (9), @audrasjb (7), @desrosj (5), @SergeyBiryukov (4), @costdev (4), @xknown (4), @tobifjellner (3), @jdy68 (3), @dd32 (3), @marybaum (3), @sabernhardt (2), @oandregal (2), @critterverse (2), @kebbet (2), @melchoyce (2), @walbo (2), @webcommsat (2), @Mamaduka (2), @johnjamesjacoby (2), @davidbaumwald (2), @peterwilsoncc (2), @vortfu (2), @chanthaboune (1), @mukesh27 (1), @mkaz (1), @kjellr (1), @ryelle (1), @annezazu (1), @paaljoachim (1), @richtabor (1), @Clorith (1), @mitogh (1), @adamsilverstein (1), @kafleg (1), @faisal03 (1), @swissspidy (1), @westonruter (1), @rachelbaker (1), @ockham (1), @flixos90 (1), @cbringmann (1), @smit08 (1), @nalininonstopnewsuk (1), @hlashbrooke (1), @sainthkh (1), @devutpol (1), @Chouby (1), @la-geek (1), @zieladam (1), @whyisjake (1), @iandunn (1), @ehtis (1), @alexstine (1), @dansoschin (1), @jameskoster (1), @noisysocks (1), @karmatosed (1), @poena (1), @robtarr (1), @felipeelia (1), @joyously (1), @ocean90 (1), and @titsmaker (1).

Congrats and welcome to our new contributor of the week: @dansoschin, @robtarr ♥️

Core committers: @audrasjb (13), @sergeybiryukov (9), @hellofromtonya (5), @davidbaumwald (4), @desrosj (4), @ryelle (3), @jorgefilipecosta (2), and @noisysocks (1).

#5-9, #core, #week-in-core