Devchat meeting summary – June 17th, 2020

@davidbaumwald led the chat on this agenda.

Highlighted/Need Feedback Blogblog (versus network, site) Posts

@davidbaumwald shared a few blog posts and announcements:

Meeting notes

@jeffpaul and @timothyblynjacobs called for particular attention to the Experimental Endpoints (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”) https://developer.wordpress.org/rest-api/. team). It needs a decision, and it could use input from a variety of experienced reviewers who understand what’s at stake:

Other meeting notes:

Upcoming releases

WordPress 5.4.2

WordPress 5.4.2 shipped with the help of our amazing contributors). This version packs six security fixes and lots of 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. fixes. More details about what is inside are on the version page.

@whyisjake took a moment to thank everyone that was part of the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. team’s huge group of contributors, both on the security front and in bug fixing.

He also called special attention to the fact that the release team decided to backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. the changes in how comments are handled to WordPress 5.1/5.2/5.3. See the related dev note for more.

As a reminder, the WordPress project’s security policy is publicly available on GitHub.

WordPress 5.5

WP 5.5 Release coordinator @whyisjake shared that 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 is roughly four weeks away, and there are still around 250 open tickets in the milestone.

Of special note is this GitHub project that the #core-editor team has been working on.

@davidbaumwald reported that he’s added the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) scrubs to the Bug Scrub Schedule for 5.5.

The Accessibility team needs help and feedback on these tickets:

@marybaum announced that there’s a team assembled to work on the About page. @davidbaumwald has opened ticketticket Created for both bug reports and feature development on the bug tracker. #50416 to handle About page development.

Following up on her announcement, @marybaum suggested promoting WP 5.5 in the current version’s dashboard for a couple of weeks in the release-candidate period in a dashboard widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user..

@desrosj answered that if something is important enough to receive its own area on the dashboard of every sitesite (versus network, blog) before it is released, the best way to do that would be in a post on the News blog.

Components check-in and status updates

@flixos90 asked the Media team for feedback on #50367.

@timothyblynjacobs would like feedback on a possible batch-processing endpoint for the REST API: #50244, on the particulars of the 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. and on the ergonomics of it.

@mikeschroder requested feedback on whether (and what) filters would be helpful for opcode cache invalidation: #36455.

Open Floor

@paaljoachim pointed out ticket #16020, which aims to introduce custom avatars for user profiles. The ticket has a patch; it needs review and final validation from the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team.

@enrico.sorcinelli called the group’s attention to ticket #21676, and @sergeybiryukov confirmed that ticket is already on his review list.

#5-4-2, #5-5, #core, #summary