Dev Chat Summary: May 17th (4.8 week 3)

This post summarizes the dev chat meeting from May 17th (agendaSlack archive).

4.7.5 Release

  • 4.7.5 was released; six security issues and three maintenance fixes, thanks to everyone who pitched in to get that out!

4.8 Timing

  • Beta 1 went out on Friday, May 12th
  • Beta 2 is due out this Friday, May 19th; potentially shepherded by @matias between 16:00 and 18:00 UTC
  • Please plan anything important before Beta 2 in by Thursday evening, May 18th

4.8 Bug Scrubs

4.8 Dev Notes / Field Guide

Location identification in Events widget

General announcements

  • Anything outside Customize, Editor, REST API, and CLI has lower priority focus in 2017
  • Major work on other components will likely not be merged or considered

#4-7, #4-7-5, #4-8, #dev-chat, #summary

Dev Chat Agenda for May 17th (4.8 week 3)

This is the agenda for the weekly dev meeting on May 17, 2017 at 20:00 UTC:

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#4-7, #4-7-5, #4-8, #agenda, #dev-chat

4.8 Bug Scrubs for Beta 1

The following bug scrubs have been planned for the 4.8 release:

Reminder that Friday, May 12th is 4.8 Beta 1 and from that point on, no more commits for any new enhancements or feature requests will be allowed in this release cycle, only bug fixes and inline documentation. Work can continue on enhancements and feature requests not completed and committed by this point, but will not be picked up for commit again until the start of the WordPress 4.9 release cycle.

As a refresher, here’s a post from the 4.7 release cycle answering questions about bug scrubs.

#4-7, #4-7-5, #4-8, #bug-scrub

Dev Chat Summary: April 26th (4.7.4 week 8)

This post summarizes the dev chat meeting from April 26th (Slack archive).

News & Updates

Target Browser Coverage

  • WordPress is officially ending support for Internet Explorer versions 8, 9, and 10, starting with WordPress 4.8
  • @voldemortensen: When patches are backported to versions pre-4.8 should they be tested against older IE versions? Are we maintaining that sort of back compat for this or once 4.8 ships we drop support for it everywhere?
    • Unlikely that anyone will test that support on backported branches
    • The “Everything else: Bugs fixed as reported.” rule from the handbook could be stretched and applied to those IE versions
    • Will continue down that path until an alternate approach for backports to versions pre-4.8 is confirmed more officially

Editor Team

  • aiming for prototype parity by the end of month
  • will gladly take any assistance on resolving issues and testing via their GitHub repo

Customize Team

#4-7, #4-7-4, #core-customize, #core-editor, #dev-chat, #summary

Dev Chat Summary: April 19th (4.7.4 week 7)

This post summarizes the dev chat meeting from April 19th (agendaSlack archive).

4.7.4 Release Timing

  • We pushed out that RC for 4.7.4 yesterday, please test it diligently
  • So far there’s been one bug report on Trac which is assigned to @azaozz: #40480: Cursor position bug when updating WPView shortcode in 4.7.4 RC
  • Otherwise no apparent activity in the forums
  • If everything goes well the plan is to release 4.7.4 by tomorrow, Thursday, April 20th starting at 16.00 UTC

REST API Team

  • A few common themes coming up while we’ve been working on with using the REST API in the dashboard
  • In particular, a common need for date handling, hooks, and i18n across various different components
  • The other two foci will either hit into this or already have, so we propose to coordinate on a common goal here (see: #39222, #20491, and #21170)
  • Propose that we nominate someone to coordinate efforts across these, including use in the Gutenberg prototype
  • Potentially someone who can look at wider, longer term plans with JS as well
  • Assumption that there’s a broad problem here, which is that we’re lacking coordination and direction for our JS stuff
  • It may help to start having core-js meetings to coordinate this, and/or for someone to take charge of the discussion
  • @aduth & @adamsilverstein will team up to lead this effort

General Announcements

  • #40462: Add placeholders to wp_login_form()
    • users in the Israeli WordPress community requesting feature
    • Previously #24324: Placeholder support to login form
    • Will add use cases to the ticket to explain why it would make sense
    • Otherwise mark it as a duplicate and keep discussion in one place

#4-7, #4-7-4, #core-customize, #core-editor, #core-restapi, #dev-chat, #summary

4.7.4 Release Candidate

After about six weeks of development, a Release Candidate for WordPress 4.7.4 is now available. This maintenance release fixes 46 issues reported against 4.7 and is scheduled for final release on Thursday, April 20, 2017.

Thus far WordPress 4.7 has been downloaded nearly 60 million times since its release on December 6, 2016. Please help us by testing this release candidate to ensure 4.7.4 fixes the reported issues and doesn’t introduce any new ones.

Notable Bug Fixes

There are a few more notable issues being addressed in this release. The first one is about broken video/audio thumbnails when uploading media (#40075). Additionally, an incompatibility between the upcoming Chrome version and the visual editor (#40305) has been solved by updating TinyMCE. Furthermore, the REST API saw some enhancements in relation to date handling (#39854, #40136).

All Changes

Here’s a list of all closed tickets, sorted by component:

Administration

  • #39983 – Consider to don’t use the CSS class button-link for controls that don’t look like links
  • #40056 – Shift-click to select a range of checkboxes isn’t working anymore since 4.7.3 update

Bootstrap/Load

  • #39445 – Add class_exists() check before defining the PasswordHash class

Build/Test Tools

  • #38500 – Automatically cancel pending Travis builds with each commit
  • #39219 – Add assertNotFalse method to WP_UnitTestCase.
  • #39367 – Don’t no-op $user_id in test suite’s wp_set_auth_cookie()
  • #39988 – The theme used during tests should call wp_head() and wp_footer()
  • #40066 – Remove the twentysixteen git clone from the Travis config
  • #40086 – Get Travis tests working again on PHP 7

Bundled Theme

  • #40216 – Twenty Seventeen: Some parts do not escape html attributes
  • #40224 – Twenty Seventeen: navigation.js should be enqueued with jQuery as dependency
  • #40264 – Twenty Seventeen: Incorrect heading hierarchy for front page sections
  • #40461 – Twenty Seventeen: Bump version and update changelog

Customize

  • #31850 – Customizer links should use canonical admin URL
  • #37471 – Widgets: If your theme only has one widget area, we should open it automatically
  • #38953 – Customize Menus: clicking outside of the available menu items panel does not close the panel
  • #39430 – sections and panels that are open and become inactive should be closed
  • #39770 – Client-side notification error is unexpectedly cleared when no corresponding server-side validation
  • #40010 – Template for site icon control fails to check if full image size exists before using
  • #40018 – Selective refresh always falls back to full refreshes when customizing the 404 template
  • #40112 – Can’t preview starter content “Home” menu item in subdirectory installation
  • #40198 – all previewable links are blocked in the customize preview on IE11
  • #40271 – Use get_user_locale() in Customizer
  • #40277 – Adding page created with the dropdown-pages settings to menu creates Custom Link instead of Page
  • #40308 – Video header control fails to use is_header_video_active() for active_callback
  • #40405 – IE9 errors when attempting to generate changeset parameter

Login and Registration

  • #39497 – Can’t log out completely without closing my browser

Media

  • #31071 – media / post_mime_type related queries are very slow on larger sites
  • #40017 – wp_get_image_mime() returns ‘application/octet-stream’ for non-image files.
  • #40075 – Broken video/audio thumbnails because of corrupted blob meta data
  • #40085 – Audio/video uploads are broken in 4.2.13 and 4.3.9
  • #40152 – Crop Image button off-screen on mobile

Networks and Sites

  • #40036 – Re-save Network Settings ruin starter content
  • #40063 – Handle site cache invalidation more specifically for option updates

Posts, Post Types

  • #39986 – Register missing REST API properties on WP_Post_Type

Quick/Bulk Edit

  • #40242 – Bulk edit tag autocomplete layout error

REST API

  • #39854 – Add gmt_offset to base /wp-json response
  • #39881WP_REST_Posts_Controller::check_read_permission() should check if $parent exists before calling itself
  • #40027 – Tags and Categories should have a “slugs” parameter for batch fetching
  • #40136 – Issues with dates and DST
  • #40213 – Users endpoint slug parameter should allow an array of slugs

Taxonomy

  • #39987 – Register missing REST API properties on WP_Taxonomy
  • #40154 – Incorrectly formatted $taxonomies parameter passed to wp_get_object_terms filter
  • #40306 – Term cache isn’t cleared completely when setting and removing object terms

Themes

  • #38292 – Introduce exclusion for WP_Theme::scandir()

TinyMCE

  • #40305 – Image popup toolbar does not support Chrome Beta

Download the Release Candidate now and help us test!

#4-7, #4-7-4, #maintenance, #release

Dev Chat Agenda for April 19th (4.7.4 week 7)

This is the agenda for the weekly dev meeting on April 19, 2017 at 20:00 UTC:

  • 4.7.4 release timing
  • REST API: Plans for JavaScript in WP 4.8
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#4-7, #4-7-4, #agenda, #dev-chat

Dev Chat Summary: April 12th (4.7.4 week 6)

This post summarizes the dev chat meeting from April 12th (agendaSlack archive).

4.7.4 Planning

  • There are currently 23 open tickets in the milestone
  • We had been aiming for an early May release, but an annoying bug (#40305, noted by @azaozz) related to TinyMCE and the upcoming Chrome release has forced us to reevaluate this strategy
  • After talking to Andrew and the security team, we decided on a new release date for WordPress 4.7.4: Tuesday, April 18, with April 20 as a fallback.
  • There will likely be an additional 4.7.5 release soon after this one

Customize Team

Editor Team

  • We’re in the long stretch of building and building, so we’re also holding “office hours” instead of weekly meetings.

REST API Team

General Announcements

  • @helen is going on leave after Friday, April 14th until August (probably 2017) (hopefully she meant 2017) (is it August yet?)

#4-7, #4-7-4, #core-customize, #core-editor, #core-restapi, #dev-chat, #summary

4.7.4 Bug Scrub

Thursday, April 13th 15:00 UTC has been scheduled for a bug scrub.

The bug scrub focus will be on tickets milestoned for 4.7.4 and the conversation will take place in #core. This will be the final bug scrub for 4.7.4 and any tickets remaining in the milestone after the bug scrub will be punted to 4.7.5 or a future release. Reminder that 4.7.4 is scheduled for release on Tuesday, April 18, 2017 with Thursday, April 20, 2017 as a fallback.

#4-7, #4-7-4, #bug-scrub

Dev Chat Agenda for April 12th (4.7.4 week 6)

This is the agenda for the weekly dev meeting on April 12, 2017 at 20:00 UTC:

  • 4.7.4 planning (bug scrub & release timing)
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#4-7, #4-7-4, #agenda, #dev-chat