Devchat summary, July 28, 2021

A week after the release of WordPress 5.8, @desrosj led a well attended but quick chat on this agenda.

Highlighted blogblog (versus network, site) posts

Jonathan drew the group’s attention to these posts:

He also added a late post of his own:

If you’d like to help with 5.8.xx minor releases, leave a comment on that post.

To-do items on 5.8

Moving on, @desrosj opened one last review of the 5.8 release and asked the group for retrospective comments and other feedback.

In reply, @chanthaboune said she’d likely have her retrospective up later in the day. And she said @matveb will shortly have some thoughts about features to target for 5.9.

Remember, also, that trunk is open now, so if you’re 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., keep committing whatever you feel is ready! (Ed. note: Plus, we’re also in alpha for 5.9, so whether you’re a committer or not, if you’re passionate about bringing a new feature into CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., now is the time to do what it takes to land it.)

Component maintainers

@sergeybiryukov checked in with news on Build/Test, where ticketticket Created for both bug reports and feature development on the bug tracker. #53363 has details on some 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 and updated naming to follow established conventions.

On U[grade/Install, Sergey added a second plug for his feedback request on the updater proof of concept highlighted above.

Open Floor

Above, in highlighted posts, you probably noticed that @desrosj asked for comments on his minor-releases post if you want to help with the 5.8.x minors. He actually added that suggestion in Open Floor.

#5-8, #core, #dev-chat, #summary

CSS Chat Agenda: July 29, 2021

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for Thursday July 29 at 21:00PM UTC. The meeting will be held in the #core-css 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/..

If there’s any topic you’d like to discuss, please leave a comment below!

#agenda, #core-css

WordPress 5.8 ‘Tatum’ Retrospective

A lot of things changed with the way that the WordPress 5.8 release was managed. A retrospective is always a good idea after a project, but in this case I wanted to be sure I cataloged the big changes for anyone who felt that it was different, but couldn’t quite put words to it. I originally shared this with the release team in Slack.

  • The teamwork had a different feeling. Instead of having buddies or cohorts of learning contributors (roughly one-to-one), we put the squad in a public channel to coordinate the work (one-to-many).
  • The release process had a different feeling. We made feature freeze independent of any other type of milestone and also are trying to be more focused about what work is done in each phase.
  • The included features had a different feeling. Instead of flipping the switch on a massive change for everyone, full site editing is being being shipped in smaller, more manageable chunks so it’s easier to catch up and we can iterate as we go.
  • The environment is different. We’ve all been struggling through this pandemic and being isolated from those we care for. Whether we recognize it or not, that has a profound impact on what we choose to do with our spare time, how we are able to meet others where they are, and whether we “grow through” or “bounce back” from hurdles that stand in our way.

Anyone is welcome to participate in this retro, so please take a few moments to fill in the form or leave public feedback in the comments below. It is not anonymous in case I need some clarification, but your email address will not be kept. The form will be open until August 15, 2021.

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

#5-8, #retrospective

Consistent minor release squad leaders for each major branch: Trial run retrospective and 5.8.x releases

During the 5.8 release cycle, a Release LeadRelease Lead The community member ultimately responsible for the Release. and Release Deputy was named for all 5.7.x releases in a trial run. The experiment was an attempt to address several pain points that made executing minor releases needlessly difficult. Each of the pain points of the minor release cycle were expanded in detail in the original post.

For the 5.7.x releases, @peterwilsoncc and @audrasjb were named as Release Lead and Release Deputy respectively. In the months between the 5.7 and 5.8 releases, they successfully planned and released 2 minor 5.7.x versions with an average of 4.5 weeks between each. The gap between the final 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. (5.7.2) and 5.8 was 9.7 weeks.

Feedback

In an effort to evaluate how this process went, they were asked for some answers to a handful of questions. Here is some collected feedback from @peterwilsoncc on how the process went.

What went well?

Generally I thought the experiment was successful and it was good to be able to concentrate (and only be expected to concentrate) on the minor releases rather than try to track both major and minor. More specifically:

  • Getting a few more people in the AEST timezone involved than usual helped with coordination.
  • Starting early my time for releases was good for the .1 version as it went longer than expected.
  • Probably should have asked for author rather than contributor permission on w.org/news so I could actually publish the posts I prepared.
  • Having scripts prepped a day in advance was great at reducing stress and allowed for dry-runs (excluding commit).

What went poorly?

  • Night owls or not, I don’t think it was great having me in APAC and @audrasjb in EU working as team leads, everything that was good about release times for me was exactly the reverse for @audrasjb (and @desrosj but to a lesser extent).
  • Better prep on the .1 release could have shortened the time for committing and moving on to the release party.
  • Needed to pull in a couple of people on the release day for the .1 release.
  • Finding someone with mission control access is not easy (especially in timezone). The list of those with permissions is really out of date, and some probably don’t need release permission any more.
  • I didn’t delegate some of the adminadmin (and super admin) stuff well and ended up doing a fair bit at the last minute as a result (on me for not asking).

What did you learn?

  • How to release 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/ packages, although doing so on my first production commits to the repository was a little brave.
  • Depending on the number of security backports, and how far back they need to go, release day for a minor can be busier than a major.
  • Process page in the handbook is quite out of date: updated a few steps after each of the two releases.

What support did you receive?

A lot.

  • @gziolo and @isabel_brison helped a great deal with getting the Gutenberg release process down, especially @gziolo by updating the undocumented steps as I asked questions.
  • @audrasjb, @desrosj and @whyisjake with release processes, both in advance and on the day.
  • Code review of shell scripts to attempt to speed up the process.
  • @dd32 with release day stuff, including catching quite a few things I was unaware of on the day.


What support could you have used?

Needed a lot more support from editor team with some planning tasks. The team was consumed with 5.8 and Full Site Editing, so they did not have much time to spare.

What were some responsibilities or tasks you had to take care of that you did not anticipate?

  • Expected I’d need to prep some release day scripts, but didn’t realize how many until I started doing them. Again, probably would have been helped by better delegation
  • Didn’t realize I’d need to do NPM releases at the start but figured it out well before the actual release

Anything else you feel is worth sharing?

Generally I think it went well and was successful.

Continuing the trial in 5.8.x releases

Because the experiment was generally successful, it will be repeated in 5.8.x releases. To reiterate the ideal criteria that was listed in the original proposal, the two contributors serving as release lead and release deputy will be responsible for:

  • Publishing timelines and plans for each minor release.
  • Executing these plans through release day.
  • Coordinating with the Security Team lead to improve the flow of fixes from the team to users.
  • Assembling and requesting help from other volunteers for each release as deemed necessary (docs, test, specific focus areas, etc.).

Ideally, one of these two contributors has a technical background (with the abilities to identify, confirm, test, and approve 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 and changes), and the other has a project manager or coordinator background (with the abilities to create release timelines, coordinate contributors, and help unblock efforts).

One additional (potentially optional) criteria would be that either the lead or deputy be a part of the previous major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.’s squad, or be very familiar with the changes that were introduced in that major release. This would further increase the speed at which the minor releases are able to fix related bugs, as they are already “up to speed” on the changes.

In recent years, the gap between major releases has been, on average, 3 to 5 months. If necessary, contributors can 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.) in and out of the role should circumstances change and it becomes necessary.

If you’re interested in volunteering as a Release Lead or Release Deputy for the 5.8.x releases, please comment below!

Props @peterwilsoncc and @audrasjb for their great work during the 5.7.1 and 5.7.2 releases, and @chanthaboune for pre-publish review.

#5-7, #5-8

CSS Chat Summary: 22 July 2021

The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes.

Housekeeping

  • No housekeeping items this week

Custom Properties (#49930)

  • @notlaura shared some background on the project for new participants and suggested another session of individual work time
  • @notlaura added a note to the trac ticket indicating who has “claimed” particular coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. files

30 or so minutes later…

  • @Dave Ryan reported having made solid progress on login.css & finding some near-duplicate shades of blue, for which he added new custom properties. Work on colour unification can come later
  • @notlaura had a similar experience with shades of grey and agreed with the approach. @Dave Ryan added a note about it to the shared doc

CSS Link Share / Open Floor

Thanks everyone!

#core-css, #summary

Dev Chat Agenda for July 28, 2021

Here is the agenda for this week’s developer meeting to occur at July 28, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

5.8 Review

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 the usual agenda items 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-8, #agenda, #core, #dev-chat

CSS Chat Summary: 15 July 2021

The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes.

Housekeeping

  • @notlaura wondered how we could encourage participation at the chats, and get more help with the Custom Properties project. She suggested maybe some guidelines on how to get started contributing
  • @danfarrow offered to add some notes to the shared document
  • @notlaura also suggested a “Call for CSSCSS Cascading Style Sheets. contributors” Make post linking to the shared document and offered to work on writing that

Custom Properties (#49930)

  • @notlaura suggested spending some time working individually on the project which is something we’ve tried at previous meetings with great success

20 minutes later…

  • @notlaura used the time to write a draft of the previously mentioned Make post
  • @danfarrow started updating forms.css noting that some custom properties have a longer ancestry e.g. --wp-admin--button--text takes its value from --wp-admin--button-primary, which in turn takes its value from --wp-admin--theme--primary. He speculated that tooling could make it easier to traverse & understand this hierarchy

CSS Link Share / Open Floor

Thanks everyone!

#core-css, #summary

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

  • 24 commits
  • 23 contributors
  • 103 tickets created
  • 18 tickets reopened
  • 68 tickets closed

Please note that as expected, WordPress 5.8 was released last week, on Tuesday July 20, 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 and/or focus.

Code changes

Build/Test Tools

  • Rename classes in phpunit/tests/widgets/ per the naming conventions – #53363
  • Rename classes in phpunit/tests/sitemaps/ per the naming conventions – #53363
  • Rename classes in phpunit/tests/blocks/ per the naming conventions – #53363
  • Move and fix incorrectly placed tests for 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. supported styles – #53363
  • Use better assertions in WP_UnitTestCase_Base::assertEqualFields(): – #53363
  • Modernize the WP_UnitTestCase_Base::assertEqualFields() method: – #53363
  • Correct placement of the $message parameter in assertDiscardWhitespace()#53363
  • Add a $message parameter for custom assertions in WP_UnitTestCase_Base#53363
  • Correct class name for WP_Filesystem_Base::find_folder() tests – #53363
  • Update PHP_CodeSniffer to version 3.6.0 – #53477

Bundled Themes

  • Version Bump 2010, 2011 and 2012 – #53777
  • Bundled Themes: Use correct path for loading images in block patterns – #53769
  • Twenty Ten: Use correct path for loading block patterns – #53752

Media

  • Check the posts_per_page value in wp_ajax_query_attachments() before using it as a divisor – #53773
  • Media: Remove unused code from wp-admin/includes/media.php#53764

Documentation

  • Miscellaneous docblockdocblock (phpdoc, xref, inline docs) corrections and improvements – #53399
  • Add a comment about the $title global usage in various adminadmin (and super admin) files – #53729
  • Correct a comment about WebP constants in wp-includes/compat.php#53680

Help/About

  • Add / character to img and source tags – #53716

Internationalization

  • Fix broken loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. in WP_Theme_JSON_Resolver

Editor

  • Conditionally load registered styles for block variations – #53616

External Libraries

  • Correct the underscore version used when registering – #53713
  • Correct the jquery-form version used when registering – #53714
  • Correct the hoverIntent version used when registering – #53715

Props

Thanks to the 23 people who contributed to WordPress Core on Trac last week: @jrf (5), @audrasjb (4), @sabernhardt (3), @david.binda (3), @hellofromTonya (2), @aristath (2), @SergeyBiryukov (1), @schlessera (1), @TobiasBg (1), @ankitmaru (1), @radixweb (1), @rtm909 (1), @GaryJ (1), @dd32 (1), @ravipatel (1), @peterwilsoncc (1), @loranrendel (1), @ryelle (1), @rudlinkon (1), @youknowriad (1), @kapilpaul (1), @2linctools (1), and @johnbillion (1).

Congrats and welcome to our 5 new contributors of the week! @radixweb, @rtm909, @loranrendel, @rudlinkon, and @2linctools ♥️

Core committers: @sergeybiryukov (17), @desrosj (3), @gziolo (2), @peterwilsoncc (1), and @johnbillion (1).

#5-8, #week-in-core

Editor Chat Agenda: 28 July 2021

Facilitator and notetaker @ajitbohra

This is the agenda for the weekly editor chat scheduled for Wednesday, 28 July 2021, 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/..

  • WordPress 5.8
  • What’s new in Gutenberg 11.1.0
  • 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/ 11.2.0 RC
  • Whats next in Gutenberg: July and August.
  • Project updates based on the latest site editing scope:
    • 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 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. Editor.
    • Navigation Block & Navigation Editor.
    • Template editor.
    • Patterns.
    • Styling.
    • Mobile Team.
  • Task Coordination.
  • Open Floor.

Even if you can’t make the meeting, you’re encouraged to share anything relevant for the meeting in the comments below:

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

#core-editor #core-editor-agenda #agenda #meetings

Dev Chat Summary: July 21, 2021

@desroj led the weekly meeting at 20:00 UTC. Here is the meeting agenda.

Link to 20:00 UTC <dev-chat> in #core on Making WordPress Slack

Notable news and blogblog (versus network, site) posts

WordPress 5.8 was released yesterday(July 20, 2021)! The new release was downloaded 7.7 million times in a little over 24 hours.

What’s next in Gutenberg?

What’s new in Gutenberg 11.1.0?

Requests for Feedback

Component Team Updates

Build/Test Tools

  • Ongoing modernization of PHPUnit tests. #53363
  • PHP_CodeSniffer updated to 3.6 (with PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 support) #53477

Auto-Updates

Themes

Open Floor

  • @desroj highlighted a bug in the Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site Filesystem 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. that was requested to be prioritized in 5.9.
  • @chanthaboune raised a discussion about Making WordPress Slack — what we can/should use it for. Should #core be the default channel? Should some other 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/. channel be created to greet new users (who may or may not have context entering Slack that it is mostly a working environment)? This was a lively discussion, please add more thoughts in the comments below!
  • While it’s been a fairly quiet (some might say too quiet) and smooth release, @chanthaboune encouraged the hosting (and greater) community to check-in with support folks and report back any trends. @johnbillion also noted a handful of tickets about Widgets have been opened related to “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. customisation and logic plugins.”

Watch For

Interested in volunteering for upcoming WordPress releases? Please comment below and team reps will reach out!

Props to @dryanpress for taking these #summary notes!

#dev-chat