Dev Chat Summary: August 14

After the close of our every-two-weeks new contributor chat, the weekly core chat started at 2000 UTC, give or take a few minutes. (backscroll)

Announcements

Next Minor: 5.2.3

Next Major: 5.3

  • All but two focus lead type people are settled. An update post is upcoming (and will be shared by the end of the week regardless of whether those final two are settled or not).

Open Floor

To Do List from this Chat

  • First 5.2.3 bug scrub Thursday, August 15 @ 1700 UTC
  • If you want to help with the 5.2.3 minor release and weren’t mentioned above, you can indicate your interest in the comments of this post.

#summary #5-2-3 #5-3 #rest-api #auto-update

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

WordPress 5.3 Planning Roundup

In Core chat, I shared three potential target dates if we wanted to have one last release in 2019. There were pros and cons to each*, but after a lot of discussion and outreach it seems that the November date is the most comfortable option.

Proposed WordPress 5.3 Schedule

To give everyone a concept of what those target dates along the way will be, I’d like to suggest these (and open the comments for discussion):

  • Beta 1: 23 September, 2019
  • Release Candidate: 15 October, 2019
  • General Release: 12 November, 2019

For some context, the dates I’m trying to avoid in November are the week of the 4th (for post-WCUS recovery), and the week of the 25th (US Thanksgiving). The 11th of November is also an observed holiday in some countries. Let me know if I missed anything.

Proposed WordPress 5.3 Scope

I’ve asked most component maintainers for an idea of what could be included in a release during this timeframe. Most of these updates are focused on polishing current interactions and making the UIs more user friendly. Some highlights are:

  • Grouping: support for dividing your page into sections
  • Motion: support for visual motion when moving/arranging blocks
  • Column patterns and widths: support for fixed column widths, and predefined layouts
  • Big images: support for saving progress after a big image fails to upload
  • Media accessibility: some fixes and a lot of polish as a result of the a11y audit
  • PHP 7.4: support for the new version coming late in November
  • And also: Build/Test updates, better administration of emails, and a lot of under the hood improvements!

Proposed WordPress 5.3 Leads

This section is still pending some answers. I will fill it in as I get Yeses and Noes from people. 🙂

  • Editor Tech:
  • Editor Design:
  • Core Tech:
  • Theme:
  • Docs coordinator:
  • Marketing/Release Comms:
  • Triage PM:
  • Release coordinator:

*The Pro and Con Summary

  • The October target feels too soon, especially with summer holidays, pre-WCUS traveling/prep/etc, and multiple events that would take contributors time. But it does let us get in all the fresh updates that have happened in the past 10 Gutenberg releases.
  • The November target is after WCUS, but should land squarely before the holiday gauntlet. It is later than October and those updates are piling up, but it also gets us ready for PHP 7.4 coming at the end of November.
  • The December target is very far away, and we would want a minor before then (discussions of that minor have been colored by concerns with complexity). We could probably keep this target as a backup in case November goes sour. 🙂

#5-3 #planning

Dev Chat Summary: July 31

This post summarizes the weekly devchat meeting from July 31st, 2019 ( Slack Archive).

Announcements

@chanthaboune reported that she was recently told what a patient and welcoming group Core is. Kudos to all for being so welcoming!

The following announcements were posted requesting feedback in the last week:

Also, PHP 7.4 has hit the beta stages and is target for public release in late November.

@kadamwhite asked what the most productive way to express support for the proposed plan to raise the minimum PHP version. The fear expressed was that +1 comments would be unproductive noise. @miss_jwo confirmed she was OK with +1 comments.

Upcoming Releases

5.3 Update

@chanthaboune has a few updates that she still needs to post.

However, after reaching out to a few people (and being proactively reached out to by several others), the picture being painted indicates an early November release is feasible. This would mean a post WordCamp US (November 1-3) but pre US Thanksgiving (November 28) timeframe.

Some attendees expressed hesitation to committing to a release date too soon after WCUS. But there seemed to be a sentiment that with enough advance notice and an early enough release candidate (early October at the latest), a date within this general timeline could work. There is currently no new default theme planned for 5.3.

5.2.3

A few people thought that 5.2.3 could still be warranted between now and November. #47797 was raised as a possible ticket (and anything else needed to prepare for a PHP version bump in 5.3) for inclusion in 5.2.3.

Component Maintainers:

The following upcoming meetings were called out by component maintainers in attendance:

  • Media – Thursday, August 1, 2019 @ 13:00UTC
  • REST API – Thursday, August 1, 2019 @ 1800 UTC

@jorbin also called out that now is a great time to make the push for PHP 7.4 compatibility. Getting the 7.4 job to pass in Travis is a good first step.

#dev-chat, #summary #5-3

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 Summary: June 12, 2019

Announcements

@marybaum graciously offered to help lead Dev Chat next week. While many folks will be at WCEU, there are many others that will not. The meeting shall go on! Thanks Mary!

WordPress 5.2.2 Updates

5.2.2 co-lead @marybaum mentioned that tomorrow the RC2 process will begin and the time was agreed to be 15:00 UTC. The following dates are the updated schedule for releases:

Release Candidate 2: Thursday, June 13, 2019, 15:00 UTC
Final Release: Tuesday, June 18, 2019

WordPress 5.3 Updates

@chanthaboune discussed timing for the release saying, “Folks with suggested major focuses have all gotten their best timing estimates to me and it’s shaping up to look pretty good. The focuses seem land-able by late Sept/early Oct, which leaves about a month before WCUS.”

Scope of 5.3 as it relates to the 9 Projects for the Year

@jeffpaul asked “Is the hope that 5.3 includes the final portions of release-related projects from Matt’s list of 9 projects for the year? Asked differently, what remains from that list that we should be aiming to include alongside 5.3?”

@chanthaboune mentioned that the block directory is currently awaiting design feedback. Next steps are to be determined and will be mentioned in a 5.3 update post.

@earnjam said the content registration features for themes seems a bit nebulous. In particular:

Porting all existing widgets to blocks.

Upgrading the widgets-editing areas in wp-admin/widgets.php and the Customizer to support blocks.

@aduth provided a very handy link on the current status of these features on the roadmap: https://github.com/WordPress/gutenberg/blob/master/docs/roadmap.md

Jeff asked a follow up question “Is of the remaining projects that are incomplete which (1) are near completion and just need some assistance or (2) are of the upmost priority to try and complete by the end of the year. Knowing the answers to those could help show folks the best places to swarm and help get projects to completion?” @chanthaboune offered to address this and the other roadmap items in a 5.3 update post after WCEU.

@clorith asked “Will this be the final release of the year, and how does that align with our plans to (possibly, depending on how 5.2 rolls along) update minimum requirements to PHP 7.x ?” This will also be addressed in the 5.3 update post Josepha offered to tackle after WCEU. @jorbin shared some great stats on the current state of PHP versions finding that “We are under 20% for below 5.6” which is a massive improvement!

Updates from component maintainers

Call for new maintainers of components:

There are a handful of components that are in need of a maintainer to watch over and nurture them:

@azaozz offered to be a maintainer of Script Loader and everyone cheered! Thank you Ozz! Discussion also took place on the collective noun for multiple Ozz, as it would be greatly appreciated to have more of them to help maintain some of the above components. 🙂

Please comment below this post if you are interested in any of the above components, or feel free to reach out to @chanthaboune if you’d rather volunteer privately.

General Announcements and Open Floor

Jonny Harris is working on a feature plugin that gives REST endpoints for menus. This is in preparation for upcoming navigation blocks, but it also serves as an excellent way of exposing menus to headless applications using WordPress. He would like some feedback on the plugin and would appreciate thoughts on considering this in the scope of 5.3. Please leave on this PR: https://github.com/WP-API/wp-api-menus-widgets-endpoints/pull/22

@presskopp mentioned a commented made here on the 5.3 call for tickets post. @chanthaboune mentioned that there is agreement and it is wrapped into the triage work from the 9 projects mentioned earlier in notes.

@bph asked, “There is a big knowledge gap that there is actually user documentation available for Gutenberg. Where would a discussion be placed best design/core-editor to surface the document within the block editor?” @aduth said that it was mentioned in a recent #core-editor chat and linked some action items from that chat here: https://wordpress.slack.com/archives/C02QB2JS7/p1558532425222200 Andrew proceeded to offer to help in creating a GitHub issues for this. @bph offered to make a post to discuss this further. More to come soon!

These notes were taken by @antpb and proofread by @chanthaboune.

#5-2-2, #5-3#devchat#summary

#5-2