Dev Chat Summary, May 25, 2022

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

Start of the meeting in #Core channel on the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

2. Announcements

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

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

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

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

  • GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 13.3 is in the process of being released today as we speak.
  • The latest core editor improvement post on container blocks and blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. locking shows off some new features to explore with row/stack/group.
  • A recap of the latest hallway hangout happened this morning on FSE topics and might be of interest to folks here.

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

4. Upcoming releases

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

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

5. Component maintainers

Build/Test Tools reported by @sergeybiryukov:

  • GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ Action Slack notifications now link to a specific run attempt. This makes it easier for someone to see the proper context of a specific notification in case of failure. See ticketticket Created for both bug reports and feature development on the bug tracker. #55652 for more details. Thanks @desrosj
  • Some instabilities (test leaks) were fixed in unit tests for comments. See ticket #54725 for more details. Thanks @hellofromtonya
  • General: The recommended minimum version for MariaDB was bumped to 10.3. See ticket #55791 for more details. Thanks @hellofromtonya, again! 
  • Date/Time, I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks: No major news this week

Update/install reported by @afragen

Sitemaps component reported by @pbiron:

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

6. Open floor

@audrasjb prepared some great stats on WordPress 6.0 contributors.

@hifidesign brought up a PR that documents pretty big bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. w/r/t to unnecessary duotone code being added to non-FSE themes #38299 and @annezazu mentioned that all of the work is being tracked in that ticket for anyone to follow up.

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

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

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

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