Dev Chat Summary: April 5th (4.7.4 week 5)

This post summarizes the dev chat meeting from April 5th (agenda, Slack archive).

4.7.4 Planning

• Bug scrub on Monday helped close additional tickets, < 30 tickets in the milestone
• Needs Patch tickets likely to be punted to next release if no progress/patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. soon
• Still aiming for an early May release
• @barry to work on resolving issue with GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/. mirror at develop.git.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ (tests not running on Travis, uncertain about build status)
• Please help test tickets, especially #40085 and #40075 as high priority tickets

Community Summit and CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team reps

• Invites to Community Summit have been sent out, please RSVP if you haven’t done so
• @desrosj, @stevenkword, & @adamsilverstein in attendance at CS and WCEU and will be Core team reps to help coordinate for CS

Customize Team

• Image widget is getting close to being ready for merge, so please test to help ensure its solid

REST API Team

• #38323: Reconsider $object_subtype handling in register_meta()
  • Looking to gather feedback on a solid approach for enhancing register_meta(), so that metadata may also be registered for specific “subtypes” only, not entire object types
  • When originally enhanced (see #35658), this functionality was stripped out in the end because of a lack of decision and since time was running out in the 4.6 cycle
  • Some discussion earlier today that culminated in #core-restapi channel
  • A problem is that Core has never before used the concept of “subtypes”, we’ve always dealt with post types and taxonomies (for example) separately
  • Will continue the technical discussion in #core-restapi or on the #38323 ticketticket Created for both bug reports and feature development on the bug tracker.
  • If anyone has further ideas on how to clarify the functionality of register_meta(), please help us out in #core-restapi or on the related GitHub issue

π

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