Brian Alexander 10:17 pm on December 13, 2023
Tags: , , , ,   

Dev Chat Summary, December 6, 2023

The WordPress Developers Chat meeting took place on  6 December 2023 at 20:00 UTC  in core on Make WordPress Slack (or #core in Matrix).

Key info

Announcements

  • WordPress 6.4.2 Maintenance & Security Release: This 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. addresses a handful of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. bugs, as well as a preventive security update. Props to the minor release squad for getting this shipped!

Highlighted Posts

Editor Updates

@annezazu has graciously shared this week’s #core-editor update, found here: https://make.wordpress.org/core/2023/12/05/dev-chat-agenda-december-6-2023/#comment-45924

Release Updates

Next minor release: 6.4.3

@jorbin indicated that work is underway to put a squad together for this release.

👉🏻 Volunteers interested in helping on the 6.4.3 minor release should drop a note in #6-4-release-leads.

Next 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.: 6.5

Some helpful links:

Are you able to help with future 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. scrubs? Bug scrubs post. Next scrub: December 19, 2023 at 19:00 UTC in the #core Slack channel.

Component Maintainer Updates

Disable autoload for large options

@flixos90 requested a second opinion and general feedback on the approach envisioned in https://core.trac.wordpress.org/ticket/42441. In order to differentiate between whether an autoload value for an option was set as a default or explicitly chosen, it is proposed to add new possible values for that database column. For additional context, comment:20 may be helpful, and a PR implementation already exists.

While personally supportive of the effort, Felix added that such a change will require a dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase., and plugins specifically focused on autoloading may need to cater for the change. It was clarified that only plugins that enhance autoloading specifically should be affected. @azaozz agreed that this approach was sound, and should be fully backwards compatible. Additional discussion moved to the Trac ticket.

Open Floor

Core version displayed on Updates page

From the agenda comments, @shenyanzhi wished to draw attention to https://core.trac.wordpress.org/ticket/40241. It was suggested to raise the ticketticket Created for both bug reports and feature development on the bug tracker. over in #core-upgrade-install for additional feedback, and for contributors to leave a comment on the ticket or dev chat post comments.

Disable the WordPress-Docs ruleset in Gutenberg

Also from the agenda comments, @antonvlasenko asked for feedback on a proposal (GB 56487) to [temporarily] disable the WordPress-Docs ruleset from Gutenberg. Core doesn’t use these rules, so this change would simplify the backporting process from Core, improving parity between the repos. Feedback on the issue or accompanying PR is greatly appreciated.

Next Meeting

The next meeting will be on 13 December 2023 at 20:00 UTC .

Are you interested in helping draft Dev Chat summaries? Volunteer at the next meeting!

Props @hellofromtonya for peer review, and @webcommsat for essential meeting preparation work.

#6-4, #6-5, #dev-chat, #meeting, #summary