Here’s what happened in the dev chat from November 22, with @marybaum facilitating, on this agenda. If you would like more detail, check out the chat transcript.
What’s new in Gutenberg 17.1
New section: core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor updates
@annezazu was in the house to kick off an experiment: instead of a separate editor chat, the editor team will have its own section for updates in the Core devchat.
In the meeting, the discussion started with a cut-and-paste of her comment on the agenda; then folks could question and comment on the items they were interested in. The result was a clear view of the huge job the editor team has been doing—and continues to polish.
The group skipped over the standard upcoming-releases section to bring up two tickets whose stakeholders particularly wanted to get eyeballs on.
#59758 went first and got a commitment to test its patch 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. from the attendee who showed up at the meeting specifically to advocate for it.
The other, #59866, got attention in a bug 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 that happened just before this summary appeared on the Make blog (versus network, site).
Thanks to the folks who helped move both those tickets in the right direction!