Dev Chat Summary: February 27th

This post summarises the weekly dev chat meeting from February 27th (agendaSlack archive).

WordPress 5.1.1 Updates

To allow a little extra time, WordPress 5.1.1 will now be released on March 12. To make the most of the available time, two bug scrubs have been scheduled. You can read more about them on the WordPress 5.1.1 schedule update post.

The are currently 18 tickets milestoned for 5.1.1.

WordPress 5.2 Updates

There was some discussion last week about the release schedule: @jorbin proposed shifting the release dates by a week. The new release dates for WordPress 5.2 are:

  • Beta 1: 21 March, 2019
  • Release Candidate: 17 April, 2019
  • General Release: 30 April, 2019

The WordPress 5.2 scope and schedule proposal included a suggestion for “feature release leads” to help keep the release running on time. If you’re interested in volunteering, please comment on that post, and mention @chanthaboune.

Updates from focus leads and component maintainers

There have been quite a few ongoing discussions around release cadences, @desrosj has kindly summarised the situation into a post. If you have thoughts or feelings on this topic, please comment on this post:

There are several tickets for plugin PHP compatibility with patches that need testing, feedback, and committing. If you’re able to do one or more of these, please lend a hand! 🙂

The work on reverting the recent bulk ticket close will be kicking off soon. If you’re a component maintainer who does not want to have tickets in your component re-opened, please ping @desrosj know.

General Announcements and Open Floor

@joyously asked about determining if there are test cases for everything, which lead to a discussion about setting up a code coverage tracker. #46373 now exists for researching options, and setting this up.

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