Dev Chat Summary: July 10

In @chanthaboune‘s scheduled absence, @ianbelanger served as the facilitator for the chat.

Announcements

@joyously called attention to the recent Make post for feedback regarding the upcoming User & Developer Survey.

Upcoming Releases

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

Currently, there are only three tickets milestoned for a potential minor before 5.3.

@audrasjb encouraged a quick decision regarding a 5.2.3 release given the current list of tickets deal with regressions. @desrosj suggested that some 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. editor features could be backported for a 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..

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. (5.3)

Final features and focuses have yet to be determined for the next major release, nor has a final schedule been announced.

Open Floor

@francina mentioned ticketticket Created for both bug reports and feature development on the bug tracker. #11302.
@ramiy called attention to ticket #35774.

This summary was drafted by @davidbaumwald and proofread by @sergeybiryukov.

#5-3, #dev-chat, #summary