@audrasjb facilitated the chat on this agenda.
Full meeting transcript on Slack
Announcements
Upcoming Releases
Next minor 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.: WP 5.4.1
While there is no release planning for the moment, there is already 12 tickets in the milestone.
2 tickets are labelled with major severity The seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs.. It will probably lead to a point 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. in few weeks.
@whyisjake will run a first bug 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 for WP 5.4.1 on Thursday April 9, 2020 at 20:00 UTC.
@marybaum volunteered to run another bug scrub on Friday.
Next major 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.: WP 5.5
There is currently 27 tickets with early keyword in the milestone. Those tickets need to be merged as soon as possible.
@davidbaumwald will run a first bug scrub for WP 5.5 on Tuesday April 14, 2020 at 19:00 UTC.
Component maintainers updates
@afragen shared a number of tickets for theme compatibility that still need eyes and are marked early. All have working patches and need further testing.
@audrasjb pointed out that the Auto-updates team needs a cross-team discussion about wording and specifically concerning the action links text labels. Design and Accessibility 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) teams could help, and of course everyone interested. Design & Wording validation is the main goal for the next version of the feature plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins..
@garrett-eclipse shared that the Privacy team has a multisite 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 focus in 5.5 so any people from Network (versus site, blog)/multisite component is welcome to assist.
Daylight saving time: devchat meeting time change
As Daylight saving time already started for every countries/locales on our planet 🌏 the devchat meeting time will be adjusted from 21:00 UTC to 20:00 UTC.
The next meeting will be held on Wednesday April 15, 2020 at 20:00 UTC.
@marybaum is going to publish a specific announcement about this adjustment.
#5-4, #5-4-1, #5-5, #dev-chat
