Dev Chat summary: January 8, 2020

The chat was facilitated by @francina on this agenda.

Full meeting transcript on Slack

Upcoming Release – WordPress 5.4

@francina reminded the main feature of 2020 will be full site editing. All component maintainers received a ping before Christmas to put together a scope for WordPress 5.4. An open call for tickets was also published on Make/Core. While @francina noted there were mostly bugfixes and not so many new features, @audrasjb raised ticket #48850 from the comments of this post. This ticket is related to automatic updates for plugins (with manual opt-in), which is one of the 9 projects for 2019-2020.

@azaozz noted that the media component team plan to continue with image post-processing. It looks like it will need couple of small UI changes/enhancements.

@audrasjb added the accessibility team will probably focus on bugfixes on both Gutenberg and Core for 5.4, and target the next major (5.5) for bigger new features.

Highlighted posts

@francina noted that a lot of volunteers signed up to the release model working group. @francina will write a recap post on Make/Core.

Worth noting @azaozz published a 5.3 release cycle post-mortem.

Components check-in

Comments: @imath is working on #35214. Feedback welcome.

Core privacy: @xkon said the privacy team won’t have any specific focuses for 5.4, only bugfixing & enhancements on existing parts. Some of them need backward compatibility review, especially #44038 and #44176. Both tickets have a patch and are ready for further iterations if needed.

Media: @azaozz is experimenting with #44427. Seems a very worthwhile enhancement for 5.4.

Open floor

In the agenda comments, @justinahinon pointed out some editing needed in the roadmap, and highlighted reactions of the community concerning handling of big media on WP 5.3. @azaozz noted most comments are about “missing” the original image in some way. The initial plan was to have a link to it in the user interface. It should be added in 5.4. Another enhancement for the UI would/may be to show when an image is missing some of the sub-sizes and have a way to create them. There are plugins that handle this, but may be time to have it in core. There are couple of pre-existing edge-cases that need fixing too. Most notably increase of the file size for indexed PNGs when resized to smaller dimensions.

@timothyblynjacobs shared #47192 as a possible 5.4 feature. It’d bring a pretty often requested feature to Recovery Mode. It would need design and copy input as well as a security review from people familiar with the intricacies of the Users/Capabilities API.

#5-4, #devchat, #release-process, #summaries

Dev Chat Summary, October 16, 2019

@francina led off a well-attended dev chat – 29 active participants! – with the standard introduction and remarked that we were in Week Nine of the release cycle.

Announcements and Highlighted Posts

She issued a call for announcements and highlighted posts, then announced that WordPress 5.3 Release Candidate 1 had landed the day before, on October 16.

@azaozz and @sergey were our packagers; @francina and @desrosj led the process.

Dev Notes

@johnbillion called the group’s attention to a crop of new dev notes as a way to keep up with changes in 5.3 for devs; @justinahinon linked to the 5.3-specific ones here.

@jeffpaul added that pending one more dev note, the Field Guide will publish shortly.

Accessibility testing in the 5.3 Admin

@francina directed the group to this report from @audrasjb on accessibility testing of the CSS changes coming to 5.3 against the 20 most popular plugins on the repository.

@francina thanked @jeffpaul for the Field Guide and @ipstenu for plugin support.

Upcoming Releases


@francina‘s call for updates prompted mostly murmurings that everything’s progressing on schedule. @azaozz pointed out there were only a couple of new tickets after RC1, and @desrosj had three to call out for reviews from other committers: #48022, #48312, #47699.

(Remember that after RC1, every commit needs signoff from two committers, not one, until launch.)

Discussion of a related ticket, #48331, followed.

Calls from Component Maintainers

@francina opened the calls from component maintainers.

@jeffpaul: Not a component maintainer update, but worth noting that during the RC1 packaging process (I believe) we confirmed that trunk would be opened back up after RC2.  That may be worth confirming here and noting in the devchat summary post which you’re reading now)

@sergey and your faithful but tardy reporter confirmed that we’ll start milestoning for 5.4 at that point, and @desrosj pointed the group to the RC1 discussion here.

The final announcement from @davidbaumwald was this:

@committers Committing to Core is now open again.  Reminder, now that we’re in RC, the dev-feedback and dev-reviewed workflow is required prior to committing, where each commit must get double-signoff.

@desrosj pointed out that 5.4 already has 94 tickets. He encouraged the group and observers (and you, dear reader!) to address these 94 tickets first or punt them if they’re unrealistic.

Open Floor

@francina had two items.


RC2 is tomorrow, October 22. @francina asked the group for a team and a timeline; discussion followed about some last-minute changes that we won’t be making tomorrow.

Workflow for the About Page

@francina also opened the floor to a discussion about whether or not the About Page can get locked down 24 hours before a release. For the most part, the group agreed that much of the page can, but there will always be a few last-minute fixes — especially for majors.

See you tomorrow for the launch of RC2!

#core, #devchat, #summaries