Dev Chat Agenda for August 21st 2019 (5.3 week 1)

Here is the agenda for the weekly meeting happening later today: Wednesday, August 21, 2019, 20:00 UTC. Please share any items you’d like to include in the comments below!

  • Announcements
  • Upcoming Release Discussions
    • 5.2.3 Updates after the latest bug scrub
    • 5.3 Kickoff (missing focus leads, general and focussed bug scrubs, development cycle guide)
  • Calls from component maintainers
  • Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #core channel, to join the meeting, you’ll need an account on the Making WordPress Slack.

#5-3, #5-2-3, #agenda, #core, #devchat

Dev Chat Summary: August 7, 2019

@chanthaboune led a lively discussion that touched on a variety of things that affect the substance and timing of version 5.3.

@marybaum took notes.

Announcements

@chanthaboune started off by thanking all the posters who commented on the Backporting Security Fixes post.

Then she pointed the group to a little light reading: a new proposal on how we auto-update old versions.

@chanthaboune‘s third announcement: after much discussion on the implementation of Minimum PHP Versions, a consensus has emerged, so here’s the plan:

Anyone running PHP 5.1.1 through 5.6 will see a warning that they’re on an outdated version and a recommendation to update.

For now, it’ll be just a recommendation and not a forced upgrade, according to maintainers @clorith and @miss_jwo.

Next Major: 5.3

Timing:

It’s time to weigh in on the target dates. The place to do it is here: https://make.wordpress.org/core/2019/08/07/wordpress-5-3-planning-roundup/

@chanthaboune said final decisions will happen this week on that post.

Default Theme:

Yes, there will be a Twenty Twenty default theme, and it will be in 5.3! The group discussed choosing a theme that’s already doing cool stuff with all the new WP features—and limiting changes to what’s required in a default theme.

@mapk will champion that effort.

Q&A:

@chanthaboune opened the floor to 5.3 questions, and here’s what came up.

@miss_jwo asked how component maintainers can get committers’ eyes on code ahead of time, and @karmatosed suggested triage sessions. With confirmation from @sergeybiryukov, @chanthaboune said there’s a workflow tag for early review.

Josepha also commented that she thinks having a dedicated coordinator for each of the last several releases has worked very well.

@joemcgill suggested naming specialty leads for the release above and beyond the editor and Core leads—for example, a design lead for things like the About page and marketing materials, at a minimum.

@desrosj then commented on the fact that the last two releases have had a designated person coordinating and publishing dev notes. He noted that meant the notes got published sooner than usual, and @marybaum couldn’t resist saying that the sooner they get written, the sooner they get edited for conversation and clarity. Or, as we’re calling it in Core, folksing up the copy, notes and strings. 😜

Ben Matthews asked when we’ll know what the feature-improvement details are, and Angelika Reisiger had a similar question about the scope of 5.3.

@chanthaboune answered that in the past, the docs maintainers aimed for the first beta, with an absolute deadline of the first RC.

@presskopp asked about news from the Triage Team, and whether there will be patches coming in for 5.3. That question led to a round of praise for regular triages and kudos for Design, Gutenberg and WordCamp Meta for using triages extensively.

Here’s a point @desrosj made:

It’s also important to note that while committing may occur as a result of triaging when tickets are just ready, the goal of the triage team is not to commit changes. The goal is to make tickets actionable. That could mean different things for tickets (committing, closing, or unblocking). There are many committers that are not actively trying to triage many tickets.

@desrosj

A final question asked about the status of XML sitemaps in Core. @chanthaboune said she’d been told the feature isn’t likely for 5.3.

Next Minor: 5.2.3

@chanthaboune said she thinks the current 5.3 schedule leaves room for a minor or two if we need it for important fixes. She added that @jeffpaul has started pulling things together for a 5.2.3. He wasn’t in the chat, so look for updates here in this very blog on that subject!

Calls from Component Maintainers

@garrett-eclipse announced a new discussion around consent and logging for user privacy. For info and to weigh in or contribute, here’s the post.

@chanthaboune brought a component need to the group: apparently user docs for the block editor need a champion. @marybaum and @paaljoachim showed interest in helping.

Open Floor

@chanthaboune asked for eyes on ticket #18857, and with that, the devchat hit the one-hour mark.

#2020theme, #5-3, #devchat, #summary

Dev Chat Agenda: July 17

Here is the agenda for the weekly dev chat meeting at July 17, 2019 at 20:00 UTC.

  • Announcements
  • Upcoming Release Discussions
    • Point release
    • Major release
  • Calls from component maintainers
  • Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #core channel in the Making WordPress Slack.

#5-3, #agenda, #devchat

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 Release (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 block editor features could be backported for a point release.

Major Release (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 ticket #11302.
@ramiy called attention to ticket #35774.

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

#5-3, #devchat, #summary

Dev Chat Agenda: July 10

Here is the agenda for the weekly dev chat meeting at July 10, 2019 at 20:00 UTC.

  • Announcements
  • Upcoming Release Discussions
    • Point release
    • Major release
  • Calls from component maintainers
  • Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #core channel in the Making WordPress Slack.

#5-3, #agenda, #devchat

Dev Chat Summary: July 3

In @chanthaboune scheduled absence, @davidbaumwald served as the facilitator for the chat.

Announcements

@desrosj called attention to the Site Health component that was added to WordPress Core earlier this week. Congratulations and many thanks to all involved in the project, and special thanks to the maintainers. If you’d like to learn more, you can read the announcement here. To get involved, join the new Slack channel for Site Health, #core-site-health.

Upcoming Releases

Minor Release (5.2.3)

Currently, there are only three tickets milestoned for a potential minor before 5.3. There was no further discussion or decision making during this week’s chat for 5.2.3.

Major release (5.3)

The schedule and potential features and focuses for 5.3 has yet to be determined. No further discussion was had related to 5.3 during this week’s chat.

Calls from component maintainers

@kadamwhite brought attention to #core-restapi Bug Scrubs being led by @timothyblynjacobs, in the run-up to 5.3. Those who can are invited to participate. Recent scrubs have been happening at 1800 UTC on Tuesdays, and they are usually announced ahead of time on the Make WordPress Core blog.

It was also announced that there will be no formal #core-restapi chat this week.

Finally, @sergeybiryukov called attention to a recent make/hosting post requesting feedback regarding a change in the recommended PHP version for WordPress. If you have additional data or an opinion you’d like to share, please comment on that post.

Open Floor

@pers requested movement on ticket #46197 for potential inclusion in the 5.3 release.

@mikeyarce mentioned ticket #34560, and asked for direction on next steps. @adamsilverstein offered to review the ticket, and will respond there.

Lastly, @justinahinon called attention to the recent creation of ticket #47644.

The next Dev Chat is scheduled for July 10, 2019 20:00 UTC in the #core Slack channel.

These notes were taken by @davidbaumwald and proofread by @sergeybiryukov.

#5-3, #devchat, #summary

Dev Chat Agenda: July 3

Here is the agenda for the weekly devchat meeting at July 3, 2019 at 20:00 UTC.

  • Announcements
  • Upcoming Release Discussions
    • Point release
    • Major release
  • Calls from component maintainers
  • Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #core channel in the Making WordPress Slack.

#5-3, #agenda, #devchat

Dev Chat Agenda: June 26

Here’s the agenda for the weekly devchat meeting on Wednesday, June 26, 2019, 2000 UTC.

  • Announcements
  • Upcoming Releases Discussion
    • Point release
    • Major release
  • Calls from component maintainers
  • Open Floor

Got something to propose for the agenda? Specific items that fall into our above-listed categories? Please leave a comment below.

This meeting happens in the #core channel in the Making WordPress Slack. See you then!

#agenda, #devchat

Dev Chat Agenda: June 19

Here’s the agenda for the weekly devchat meeting on Wednesday, June 19, 2019, 2000 UTC.

  • Announcements
  • Upcoming Releases Discussion
    • Point release
    • Major release
  • Calls from component maintainers
  • Open Floor

Got something to propose for the agenda? Specific items that relate to those listed above? Please leave a comment below.

This meeting happens in the #core channel in the Making WordPress Slack. See you then!

#agenda, #devchat

Dev Chat Agenda: June 12

Here is the agenda for the weekly devchat meeting on Wednesday, June 12, 2019, 2000 UTC.

  • Announcements
  • Upcoming Releases Discussion
    • Point release
    • Major release
  • Calls from component maintainers
  • Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #core channel in the Making WordPress Slack.

#agenda, #devchat