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

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

5.0 Planning and Updates

• We started with a reminder that RC1 is out and moved quickly into a lively discussion about remaining blockers, timing, and general logistics. I’ve summarized them the best I could below.
  • There was a request for review on one outstanding item in the default theme.
  • There were requests for consideration on 11973, 6177, and 45407 in media. These tickets are largely about how to best handle responsive images, specifically some nuance around the sizes attribute.
  • There are no automated tests for expected vs actual behavior
  • This affects only new posts, or newly edited posts.
  • It’s related to full-width images in the new editor and further complicated by the lack of any way to filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. for blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. alignment width.
  • There are concerns about high data usage and negative impacts on search engines (esp for mobile)
  • Q: If we fix this in 5.0.x, what happens to content published in between 5.0 and 5.0.x? Will content need to be updated to correct? It was suggested that fixing the insertion of full size images in content and incorrect width attributes would let us ship and then iterate. Insertion is already fixed, so it’s just the second one!
  • Q: What would need to be fixed or added to content to allow it to be fixed post-release? Ensure we have correct default height and width attributes on inserted img elements.
  • We started running low on time, but additional clarifications were offered in #core-media. Additional discussion can take place on https://github.com/WordPress/gutenberg/issues/6177
• There were a number of questions that got interjected during the discussion, that I’ve collected the best I could below.
  • Are we proceeding with the January slip date as identified in the launch post?
    • A January date was seconded by the docs team and a collection of others.
    • Many mentioned concerns around predictability and user trust.
    • Data is still being gathered about how RC1 is being received, and once enough is available, a CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. P2P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. post will be made to help people plan. RC2 is next on the horizon.
    • How much time will there be between the announcement of the release date and the actual release date?
  • Are there any dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. that need to be posted prior to release? And if so, is there a list? And how can we help?
  • Should we prep a 4.9.9 in order to be prepared for PHP7.3 support?
  • There were multiple offers to help gather necessary data to determine how close we are to a release date.

Component and Focus Updates

• The PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher team shared last week’s meeting recap which included some discussion of Tide, whether to expose PHP compat on plugins/themes, and best ways to identify those with compatibility concerns. https://make.wordpress.org/core/2018/11/26/php-meeting-recap-november-19th/
• The JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. team shared this week’s meeting recap which included discussion of Contributor Day at WordCamp US, work on docs parsing for devhub, and ESLint configurations. https://make.wordpress.org/core/2018/11/27/javascript-chat-summary-november-27-2018/
• Design has a new research channel in the works. A lot of their initial work will be around user research for Phase 2+ of Gutenberg. Not much going on, but worth knowing about for sure. 🙂 https://make.wordpress.org/design/2018/11/19/two-ways-to-get-involved-in-gutenberg-user-research/

Next meeting

The next meeting will take place on Wednesday, December 5 21:00 UTC in the #core SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on the upcoming agenda post so that we can take them into account.

#5-0, #a11y, #core, #core-editor, #core-js, #core-media, #core-php, #core-restapi, #dev-chat, #gutenberg, #summary, #team-reps