Dev Chat Summary: March 27

This post summarizes the weekly devchat meeting from March 27th, 2019 ( Slack Archive ).


5.2 updates

The release did not meet original schedule for betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 but is back on track and beta release process will have been kicked off by the time you are reading these notes. Gary said, “There are currently 116 open tickets, which can be reasonably tackled in 3 betas.” The current goal is getting that down to 66 open tickets before beta 2. Target release for 5.2 is April 30. More info here:

Coding standards changes up for discussion: Be on the lookout at /news for wider awareness to the update.

Calls from component maintainers

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. crew have published a post on how to build plugins that use modern JavaScript, which I’m sure they’d appreciate feedback on:

Editor folks have a 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. registration RFC that that’d love your input on:

@desrosj mentioned #46195 and it was agreed the latest 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. can move it forward as long as we provide 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. on edge cases.

Open Floor

@elrae asked “Will the Classic Editor continue to disable other parts of GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. as it rolls out? Specifically widgets and menu areas?” This is still to be determine but @pento mentioned, “Widgets and menu areas are much more contained, on the other hand, and can likely be made largely backwards compatible.”

@dmsnell mentioned #46199 which is a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. causing some unexpected editor crashes. We would love for someone familiar with the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) to look into it. @pento said, “I think your patch looks like a reasonable change, but I’d like to get some input from some REST API folks before we commit it.”

@peterwilsoncc provided a very important reminder about being welcoming, “I’ve noticed a few facepalm, eye-roll and similar emoji reactions in SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at to tickets reported against long term design decisions of WP. Often these are from new contributors. Can everyone please avoid these as they can be intimidating for potential new contributors lurking in the room to get a feel for the project. I’ve experienced this feeling myself, lurking elsewhere to get the lay of the land.”

See you next Wednesday at the new Dev Chat time of 20:00 UTC. This adjustment is as a result of daylight savings time.

These meetings are held in the #core channel in the Making WordPress Slack.

#5-2 #devchat #summary