Additional REST API bug scrubs scheduled through October

Meeting notes for the October 11 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/. component chat will be posted by Tuesday, but one item we discussed was @danielbachhuber‘s request to run one additional 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.-scrub meeting each week for the next several weeks.

As noted in the REST API outstanding Gutenberg/5.0 issue list post and the notes from last week’s meeting, we have a number of outstanding tasks that need developer attention, and @danielbachhuber is requesting that developers commit to addressing bugs with a one- to three-day turnaround time after taking an issue. (If this is not possible—and it isn’t, for some of these bigger issues—that is alright; but it helps keep things moving if we check in on that schedule). Adding one additional bug scrub each week lets us evaluate our progress and commitments, and reassign in-flight bugs as contributor availability requires.

Upcoming REST API meetings through the end of October:

The Tuesday bug scrubs have been moved up 1-2 hours from the time of the normal weekly meeting to better accommodate European contributor schedules. We encourage all interested developers to attend any and all of these meetings as you are able, we will be excited to help you find a useful ticketticket Created for both bug reports and feature development on the bug tracker. to move us towards 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. https://wordpress.org/gutenberg/ and 5.0!

Edit: All meetings will be held in the #core-restapi 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!

Granular Timeline

As promised, here is a link to the list of dates I am tracking. I asked every named component lead in the release post what items/dates could 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. progress in their focus.

A few pieces of context that will be helpful as you look at this document:

  • My work is focused on the 5.0 release, so those are the items I have in this document.
  • Not every item or date is included, generally because it has no contingencies.
  • Not everyone has given me their items and/or dates yet. There is some educated guessing happening in here.

https://docs.google.com/spreadsheets/d/139Z7iyCoRCGucr-i5qwAcL2PqH60MLKSksOaP_hmn6w/edit#gid=0

This document is updated every day and I’ll post regularly with notable changes, including any items that are at risk so that people will have an idea of where they can focus their time.

A few people in the chat this week raised their hands with things that needed to be added to this doc. Feel free to leave them in the comments and I will either add them or share where they are already accounted for.