Dev Chat Summary: February 13

This post summarizes the weekly dev chat meeting from February 13th (agendaSlack archive).

5.1 updates

5.1 is currently on target for the Feb 21 release date.

RC1 went out last week. Two remaining bugs have been fixed (remaining open tickets can be tracked here). Right now, all that is left is the About page, which needs some design work and some minor bug fixes. @pento expects to release a small RC2 either late this week, or early next week.

The WordPress 5.1 Field guide is out, thanks to the hard work of @desrosj, @jeffpaul, and the many contributors who wrote individual dev notes for this release.

Since the meeting adjourned, 5.1 has been branched, and Trunk is open for 5.2–alpha enhancements.

5.2 and 5.1.x Logistics

Release target and cadence

Based on the desire to update the PHP requirements in April, @pento proposed targeting late April for a 5.2 release. That leaves about a month for alpha, a month for beta, and two weeks for RC.

@youknowraid proposed shortening the release cycles for WordPress to shorter, predictable cycles that are time-based instead of feature based. After some discussion, @chanthaboune suggested an official proposal be drafted on https://make.wordpress.org/core, and @desrosj volunteered to help draft the post.

Potential features for 5.2

While there are no firm commitments, a few ideas for 5.2 features include:

  • Gutenberg performance and UX improvements
  • Core widgets converted to blocks
  • PHP Fatal Recovery (WSOD)
  • Site Health Check

5.1.X Releases

Barring any major regressions in 5.1, the target for a 5.1.1 release will be 2 weeks after 5.1. With 5.2 targeted for April, 5.1.x releases will be limited to 5.1 regressions and important bug fixes that would be good to get out earlier, and exclude additional features or enhancements.

Updates from focus leads and component maintainers

An initial implementation of CODEOWNERS file in Gutenberg was merged, which is kind of a joint JavaScript and Gutenberg update.

From the Gutenberg desk: there is a lot from last week’s meeting, but there is a call for reviewers that’s worth taking a look at.

From Media: the team did a ticket triage and left excellent notes with calls for testing and patches.

From the JavaScript desk: There’s a request for feedback from @youknowriad on how to tackle selecting data over multiple stores.

General announcements and open floor

The Navigation block is currently being discussed and there are mockups in GitHub that would benefit from people’s feedback.

@afercia proposed an audit of the project’s components and maintainers soon to ensure the project is properly organized to maintain all parts of the codebase and increase participation where necessary.

Additionally, @afercia recommended that all components and teams use the correct headings level when authoring a post, and please refrain from using emojis or other extraneous content within the headings. This relates to an ongoing effort to improve the headings hierarchy across the .org network.

Finally, @chanthaboune published a post titled, Strengths and Challenges: Follow Up, earlier this week. Everyone should read it, as it applies to all teams. Additionally, she is working on the first “Scrum of Scrums/Weekly Digest/Wayfinding” post, which she expects to publish later this week.

#5-1, #core, #dev-chat

Dev Chat Summary: January 30th

This post summarizes the weekly dev chat meeting from January 30th (agendaSlack archive).

5.1 updates

Beta 3

5.1 Beta 3 was delayed by 24 hours following issues with the PHP error recovery (aka WSOD) feature. The current plan is to release beta 3 a few hours following the dev chat today.

Schedule update

Remaining planned schedule dates remain the same, with RC 1 and a hard string freeze on February 7 and a final release planned for February 21.

See also: WordPress 5.1 Development Cycle

Dev notes status report

All but three dev notes planned for 5.1 have been published

@desrosj is continuing to coordinate 5.1 dev notes. There are also plans to release a Field Guide for 5.1 on the day that RC1 is released. If any component maintainers have information they would like to have included in the Field Guide, please provide them to @desrosj before February 6, 2019.

Updates from focus reps and component maintainers

Meeting notes and summaries

Other calls/proposals

  • The REST API team is aiming to have owners for every ticket milestoned for WordPress 5.2, so could use more help if people are looking for tickets to work on.

PHP error recovery (WSOD) update

Earlier this week, security concerns were raised about this feature, which ultimately has lead to the decision by the #core-php team to revert this feature from 5.1 and try again in 5.2 in order to adequately address the issues identified. For additional context, people can reference the original ticket (#44458) and the new ticket created to track new refinements (#46130).

Continued work on this feature will be coordinated in #core-php on Slack and during weekly meetings on Mondays at 16:00 UTC.

Additional follow up

  • @flixos90 is in touch with the original reporter of the security concern.
  • @aaroncampbell agreed to follow up with the author of the ZDNet article to inform them about the feature being removed. The article has since been updated to reflect this change.
  • From a marketing perspective, @joostdevalk reminded that because of the open nature of our project, these kinds of things are going to happen, which isn’t itself a concern, as long as we are actively following up.

Open floor

@kadamwhite mentioned that the upcoming Gutenberg roadmap would likely require enhancements to the REST API in Core and suggested that there be closer coordination between the editor team and the REST API team regarding implementation of new features or enhancements.

It was suggested that when new features require knowledge from other teams, that the people working on those features reach out via component slack channels or in comments to component/team meeting notes, which should be published consistently by all active teams.

#5-1, #dev-chat

Dev Chat Agenda: January 30

Below is the agenda for the weekly devchat meeting on Wednesday, January 30, 2019 at 21:00 UTC:

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-1, #agenda, #core, #dev-chat

Dev Chat Summary: January 23rd

This post summarizes the weekly dev chat meeting from January 23rd (agendaSlack archive).

5.1 updates

Beta 2

5.1 beta 2 went out earlier this week.

There are a few tickets still open, most of them are related to fine tuning the WSOD handling.

Schedule update

Beta 3 is scheduled for January 29, this is also the soft string freeze. All string changes must be committed by then (except for the About page).

See also: WordPress 5.1 Development Cycle

Dev notes status report

5.1 is being accompanied by a nice collection of dev notes, mainly from Make/Core but also from Make/Polyglots.

@desrosj is continuing to coordinate 5.1 dev notes. There are also plans to construct a 5.1 Field Guide that summarizes collects all dev notes.

Updates from focus reps and component maintainers

Meeting notes and summaries

Other calls/proposals

Open floor

The Gutenberg Team is looking for more pull request reviewers. If you’re interested, please touch base with them in the #core-editor Slack channel. Details to be shared soon in a Make/Core Post.

About including recent Gutenberg changes in the currently scheduled release: the WordPress 5.1 cycle is being a bit stricter about non-regression bug fixes landing during the beta period, but WordPress 5.2 is expected to be able to take bug fixes during the WordPress beta period.

About the recent Post concerning the bulk edit process: many relevant opinions and thoughts were shared during the meeting.

  • @matt expressed a desire to reopen the tickets closed in the recent bulk edit.
  • @desrosj and @jeffpaul will work on a strategy for reverting closed tickets that have not been changed since the bulk edit, to allow the tickets to be properly evaluated for closure.
  • Component maintainers to review related tickets (via this custom query). However, the 5.1 release is probably going to delay the ability to do that.
  • Contributors can also use this Trac report (replacing “myusername” with their username and scrolling to those updated on January 4th) to find the tickets they have been involved with that were affected by the bulk closing.
  • A stale keyword and/or status was discussed as a good way to leave tickets open long term and avoid closing them as wontfix and maybelaterstatuses.
  • A post on Make/Core is coming next week to kick off the efforts of the new Triage Team.

This Dev Chat Summary post is open for further comments and discussions.

#5-1, #dev-chat

Dev Chat Agenda: January 23rd

Below is the agenda for the weekly devchat meeting on Wednesday, January 23, 2019 at 21:00 UTC:

  • 5.1 updates:
  • Updates from focus leads and 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-1, #agenda, #core, #dev-chat

Dev Chat Agenda: January 16th

Do you like devchat? I like devchat. This is the agenda for the weekly devchat meeting on Wednesday, January 16 2019 at 2100 UTC:

If you have anything to propose to add to the agenda or specific items related to those listed above, please leave a comment below. Either way, we look forward to seeing you at the devchat this week!

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

#5-1, #agenda, #core, #dev-chat

Dev Chat Summary: December 19

Dev Chat Scheduling

Here’s a reminder that the normal meeting won’t be happening on December 26, though there are likely to core folks around to answer questions for an open floor session. We’ll resume normal dev chats on January 2.

5.0.2 Update

WordPress 5.0.2 has just been released! Thank you to everyone who contributed.

5.0.3 Schedule and Scope

The following timeline has been proposed for WordPress 5.0.3:

  • Release Candidate: January 7, 2019.
  • General Release: January 9, 2019.

There have been some bugs reported in the MIME type handling changes in 5.0.1, these would be good to fix in 5.0.3. Additionally, there are bug fixes in the block editor which could also land.

5.0.3 will need a release lead: if you’re able to help out, please comment on this post, or reach out directly.

5.1 Schedule and Scope

Feedback on the proposed WordPress 5.1 schedule has all been positive, so let’s lock it in!

Milestone Dates

  • Beta 1: January 10, 2019
  • Release Candidate 1: February 7, 2019
  • General Release: February 21, 2019

The primary feature focuses for 5.1 will be the PHP upgrade notice and plugin error protection, and block editor enhancements.

There have been some minor features already merged into trunk, but nothing that will need to be reverted.

#dev-chat #summary

Dev Chat Summary: December 12th

Dev Chat Scheduling

As many folks will be away over the Christmas/New Year period, the next few meetings will be as follows:

  • December 19: Normal meeting.
  • December 26: Normal meeting will not be happening. There are likely to be core folks around to answer questions for an open floor session.
  • January 2: Normal meeting.

5.0.2 Schedule and Scope

Please note that WordPress 5.0.1 has just been released, so any previous mentions of scope or schedule for WordPress 5.0.1 should now be read as applying to WordPress 5.0.2.

WordPress 5.0.2 is intended to be released two weeks after WordPress 5.0, which would make the release date December 20. To give a little more space before the Christmas/New Year holiday period, I’ve proposed that it be released December 19.

Milestone Dates

  • Release Candidate 1: December 14, 2018
  • Release Candidate 2 (if needed): December 17, 2018.
  • General Release: December 19, 2018.

The following items are in scope for the 5.0.2 release:

  • Gutenberg 4.7 was released today, the fixes in this plugin release will also be in WordPress 5.0.2.
  • Twenty Nineteen bugs and visual issues.
  • There are a few PHP 7.3 compatibility fixes to be made.

Any other tickets currently milestoned for 5.0.2 will be considered on a case-by-case basis, priority will be given to tickets with patches, testing, screenshots, and any other relevant information to show that they’re ready to land immediately.

5.1 Schedule and Scope

As there are already over 200 tickets fixed in WordPress 5.1, I’d like to propose that WordPress 5.1 has a relatively short release cycle.

Milestone Dates

  • Beta 1: January 10, 2019
  • Release Candidate 1: February 7, 2019
  • General Release: February 21, 2019

A key point from the WordPress 5.0 cycle was that it demonstrated the value of having a hard feature freeze at beta 1, as well as string freezes and strict bug fixing policies during the release candidate phase. With that in mind, I’d like to propose that we retain these policies for the WordPress 5.1 cycle.

The tickets already fixed in WordPress 5.1 need to be reviewed, to ensure they’re all stable for release in this cycle.

Apart from that, the PHP upgrade warnings and the White Screen of Death protection from the Site Health Check project are currently the only uncommitted features scheduled for WordPress 5.1. The PHP upgrade warnings are currently soft warnings, ahead of the minimum PHP version bump proposed for April 2019.

@matt will be continuing his role as release lead into WordPress 5.1. Any other feature proposals will need to be approved by him.

Please leave feedback on this post, so the scope and schedule can be confirmed in the next day or two.

Focus and Component Updates

REST API

The REST API group will be re-opening discussion around authentication solutions. They’ll be posting further information about this project on make/core.

Core JS

The Core JS group didn’t meet this week, due to many folks travelling home from WCUS. They’ll be resuming normal meetings next week.

Core Themes

The current themes focus is on triaging Twenty Nineteen issues for 5.0.2, as well as preparing to move activity from GitHub into Trac. This move will likely happen immediately after 5.0.2.

#5-0-1, #5-0, #5-1, #core, #dev-chat #summary

Dev Chat Agenda: December 5th (5.0 Week 10)

This is the agenda for the weekly devchat meeting on December 5th, 2018 at 21:00 UTC:

  • 5.0 Planning and Updates
  • Updates from focus leads and component maintainers
  • General announcements

If you have anything to propose to add to the agenda or specific items related to those listed above, please leave a comment below. Either way, we look forward to seeing you at the devchat this week!

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

#5-0, #agenda, #core, #dev-chat

Dev Chat Agenda: November 28th (5.0 Week 9)

This is the agenda for the weekly devchat meeting on November 28th, 2018 at 21:00 UTC:

  • 5.0 Planning and Updates
    • A discussion about getting #11973 in 5.0 has been requested. https://github.com/WordPress/gutenberg/pull/11973
  • Updates from focus leads and component maintainers
  • General announcements

If you have anything to propose to add to the agenda or specific items related to those listed above, please leave a comment below. Either way, we look forward to seeing you at the devchat this week!

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

#5-0, #agenda, #core, #dev-chat