Dev Chat Summary: March 30, 2022

1. Welcome

The agenda followed in this week’s WordPress developer chat meeting.

Link to the start of the meeting on Slack

Meeting facilitated by @marybaum and @webcommsat.

2. Announcements

What’s new in Gutenberg 12.9 (March 30, 2022)
A big thanks to the team in getting this out earlier so we can include it in the dev chat meeting.

3. Blogblog (versus network, site) posts for dev chat awareness

  • A Week in Core (March 28, 2022)
  • Ask your questions on the Full Site Editing (FSE) program – this third round closes on March 30, 2022
  • The new pattern creator is live – you can build, edit, and submit 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. patterns to the Pattern Directory. Open to anyone with a WordPress.org user account.
  • Enabling WebP by default – thanks to @adamsilverstein for this great summary of the feature. (March 28, 2022)
  • Examples for extending WordPress/Gutenberg with blocks – GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ repo. Call for reviewers and new examples, @welcher
  • Learn WordPress Social Learning spaces MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. has regular discussions by @DaisyO on Block Themes on Fridays via WordPress Social Learning

@annezazu: hoping to have a new call for testing for the FSE Outreach program out this week if I can. She has a fun idea planned that will explore creating a new type of template, using block locking, and more. Stay tuned in #fse-outreach-experiment channel on 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/. for an announcement on when it is live.

Thanks to everyone who has contributed to posts and gives their time. You are all awesome!

4. Updates on the Releases

a) Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.0

 Bug Scrub schedule for 6.0 and that this list is regularly updated.

Update on the 6.0 walkthrough planned for 5 April 2022.

Update from @annezazu:

WordPress 6.0 continues to progress nicely! Outside of the product walkthrough next week and enabling WebP by default updates, I wanted to highlight a few things:

  • 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/ 13.0 RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). (the last Gutenberg release for inclusion in 6.0) is likely going to be pushed by a few days to Friday, April 8th to allow for more time for PRs ahead of feature freeze/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. This has happened the last few major releases so is in line with what’s worked in the past.
  • There is a new issue to coordinate backporting PHP changes for WordPress 6.0. This is a current priority for the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor tech leads. Earlier at the core editor meeting, @gziolo  invited everyone who worked on the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher changes in this WordPress release cycle to check the issue and report the status of the code introduced.
  • I’ve proposed a new role for the release squad that’s under consideration for Core Editor Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. lead to help ensure feedback shared in the Gutenberg GitHub repo is properly handled/flagged/etc. This is meant to buttress current triage efforts and provide a layer of focus.

Update from @peterwilsoncc

I’ve spent the last few days going through tickets marked early to evaluate how close they are to a suitable 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.. As the definition of early is really being stretched by now, I’ve been bumping a few of those. There are still a number of enhancements on the milestone that need reviews and/or patches so if committers could look at those.

@Craig Francis has been working on a patch for #52506, I’ve asked for second, third and fourth eyes on it from some committers and shared it with the security team for review.

Next minor: 5.9.3

@audrasjb: releasing WP 5.9.3 RC 1 after dev chat. Everything has been committed. @sergeybiryukov will handle mission control. The milestone is cleared and the announcement post is ready for Make/Core. Everyone is welcome to help test the package.
Final release is scheduled for Tuesday April 5, 2022. [Date updated]
Post meeting update: 5.9.3 RC1 release is out.

5. Open Floor

TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. Ticketticket Created for both bug reports and feature development on the bug tracker. 55015

@webcommsat: From the 5.9.3 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 on Monday, we have this ticket #55015 that needs a patch. The bug is reproducible.

@audrasjb: the ticket title doesn’t reflect very well the real issue. It happens on sites running with WP in a sub-directory and needing access to the default themes, like, for example, on Bedrock-like envs.

@annezazu to follow up.

Request from @gziolo
There is a tracking issue to coordinate the process of backporting PHP changes from the Gutenberg pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party to WordPress core. They will use Gutenberg issues ticket 39889 to audit all the new functionality added. They want to ensure it’s ready and meets all WP core requirements. Following the recommendation from @peterwilsoncc, they want to use smaller patches for this WordPress release to make the whole process smoother.

Trac Ticket 55121
@sc0ttkclark: requested some consensus on this #55121 for 5.9.x .
@peterwilsoncc: There was a decision on approach a few weeks ago but I haven’t had time to work on a patch (not just for this ticket). 

Trac Ticket 48222
@sabernhardt: #48222 ‘Show password’ button overlaps with the LastPass icon. Requested more attention on this ticket. It makes a significant change to the password visibility toggle button on (only) the login screens.
@clorith highlighted related tickets: #3534 and #9883 to try and get a unified solution.
@peterwilsoncc has added comments, and favors a single unified solution too.

Trac Ticket 19859
#19859 Bulk edit missing the ability to add tags. This has been highlighted in the component bug srub. @paaljoachim has added a comment today to help take it forward. @joedolson is looking at other bulk edit tickets and will look at this too.

Reminder: bug scrub for the Bulk Edit/ Quick Edit component, Mondays 20:00 UTC in the core Slack.

@bph: Every Thursday, Ryan Welcher runs live programming streams at 14:30 UTC on his Twitch Channel covering block and Gutenberg development topics. Tomorrow he will work on how to create a plugin custom setting screen in preparation for his WCEU Workshop.

Next meeting: 6 April 2022, 20:00 UTC

Props to: @marybaum and @webcommsat for facilitating the meeting, @webcommsat for the dev chat summary, and to @annezazu and @audrasjb for the review.

Could you volunteer next week for the summary?

#5-9-3, #6-0, #dev-chat, #summary

Dev Chat Summary: March 23, 2022

@marybaum and @webcommsat led today’s developers chat meeting. The meeting agenda.

Link to this <dev-chat> on Making WordPress 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/..

Notable news and blogblog (versus network, site) posts

Upcoming Releases

WordPress 6.0 is in active development, with plans for betas by mid-April, RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta).’s beginning early May and final release at the end of May 2022. The bug scrub schedule and list of early tickets.

WordPress 5.9.3 is planning a release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). for March 29 and final release on March 31 (or April 5, depending on final scope).

Open Floor

  • @afragen is seeking comments and feedback on Plugin Dependency iteration in #22316.
  • @craigfrancis is seeking testing and feedback on an escaping method for table names in SQL queries #52506.
  • @johnbillion noted #47280 is seeking review for the deprecation of SQL_CALC_FOUND_ROWS in MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. 8.0.17 — he and Craig are each reviewing each other’s database tickets.
  • @webcommsat mentioned two tickets from the recent 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. scrubs:
    • Ticket #19907
    • Ticketticket Created for both bug reports and feature development on the bug tracker. #33885: meta_form running a potentially expensive query as a ticket that could use more eyes and review.

Watch For

  • 6.0 bug scrubs in the coming days and weeks.
  • Just over one week to WordPress 5.9.3 minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality..
  • Just under three weeks to WordPress 6.0 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.
  • Our next Weekly Developer Chat in #core on Wednesday, March 30, 2022 at 20:00 UTC.
  • General updates & podcast episodes on WordPress News.

Props to: @dryanpress for writing the summary, and @marybaum and @webcommsat for running the meeting and reviewing the summary.

#6-0, #dev-chat, #summary, #week-in-core

Dev Chat summary, March 16, 2022

Updated 22 March with additional links

@marybaum and @webcommsat led the weekly WordPress Developers Chat meeting on this agenda.

Link to start of the meeting in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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/. of Making WordPress.

1. Announcements

A security release, WordPress 5.9.2, landed on Thursday.

There is a bug-scrub schedule for 6.0!

2. Blogblog (versus network, site) posts of note

A Week in Core from @audrasjb

The 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. Pattern Directory is testing the submissions process.

The next Gutenberg Developer Hours will happen March 22, 2022.

What’s New in Gutenberg 12.8 post

3. Upcoming Releases

(Note: The agenda skipped item 3 and called Upcoming Releases item 4. I correct that here.)

3a) The next major is WordPress 6.0.

Core Tech Lead @peterwilsoncc gave an update: A new Slack channel, #6-0-site-editor-merge, will be the home of discussions about merging the editor into Core. Also, feel free to check out the #6-0-release-leads channel, to stay up to date on progress.

Peter also noted that he’s been going through the enhancements milestoned for 6.0 and reviewing the code in patches and pull requests. He could use some help, he said, pointing out that these enhancements are due to commit before 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. (Ed. note: Remember that Beta 1 freezes features and enhancements for the release.)

3b) The next minor is 5.9.3.

@mamaduka and @audrasjb will publish a schedule on Make/Core (that’s this very site) by the end of this week.

JB will also run a 5.9.3 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 today, Thursday, March 17, and another on Monday, March 21, 2022. Both will be at 20:00 UTC.

4. Open Floor

Open floor Slack thread.
@jeffpaul asking about the future of the Debug Bar plugin.

@nalininonstopnewsuk brought up several tickets from the Help/About and Bulk/Quick Edit component bug scrub on Monday. Link to the Slack thread for the bug scrub.
Request for more input on ticketticket Created for both bug reports and feature development on the bug tracker. #41833 to help find a way forward.

@bobbingwide raised ticket #13459, with @davidb and @jeffpaul.
Please give time to these tickets.

Next meeting: March 23, 2022, 20:00 UTC in the Core Slack.

Summary notes by @marybaum

#6-0, #core, #dev-chat, #summary

Dev Chat summary, March 9, 2022

(Update March 11, 2022: 6.0 Planning Update )

Start of the meeting on the Make WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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.

Dev Chat agenda, March 9, 2022

Dev Chat summary, March 2, 2023

1. Announcements

The Performance Team has released its first plugin!

2. Blogblog (versus network, site) posts of note

  • From @audrasjbA Week in Core, March 7, 2022
  • From @annezazuA Core Editor Improvement: Choose your Style
  • From 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/ Times: Introducing the Museum of Block Art
  • Really helpful series on improvements to the core editor thanks to @annezazu and others. Choose your style. This is part of a series dedicated to highlighting new features, improvements, and more to discover the various Core Editor related projects. Just click on the tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) #core-editor-improvement tag in the Make WordPress core blog to keep up-to-date on this.

3. Upcoming releases

a) Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. 6.0

A great source of information about the next release is the 6.0 release development cycle section on the Make WordPress core.

Release co-ordinators: @annezazu has agreed to be a co-release coordinator this week alongside @priethor.

Progress for 6.0: the biggest pieces are moving along for the core editor including Styles engine, pattern integration, improvements to 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. theme creation process, and improvements in the works for switching to block themes.

Editor Tech Lead: @jeffpaul: any traction on confirming the Editor Tech Lead? @annezazu advised the core editor tech lead is known and in progress of being resolved. She will update in dev chat and agreed it is critical to have this role in place.

Bug scrubs for 6.0

  • Five weeks out from 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, query on 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. scrubs. Suggestion to add a bug scrub schedule to the 6.0 development cycle page when it is available. @annezazu to follow up on what is missing on bug scrubs.
  • Update post dev chat: @costdev is joining as a co-Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. lead. The change has been updated on the release page. It allows us to have great timezone coverage for the squad in a very important role. Next step: to get a bug scrub schedule in place (more context).

@webcommsat: On March 14, 2022, at 20:00 UTC, bug scrubs on the About Page and Quick/ Bulk Edit components will begin. Requested to @marybaumand @audrasjb for these to be added to the bug scrub schedule.

b) 5.9.2 Next Maintenance Release Update:

  • Trac tickets (1 already backported and 4 ready for 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., on 22 tickets)
  • GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ issues (22 fixed, on 69 issues): https://github.com/WordPress/gutenberg/projects/63

@audrasjb and @mamaduka will publish a release schedule on Make/Core for the next maintenance release in the next couple of days.

c) Gutenberg

Released Gutenberg 12.8 RC1 in the #core-editor channel.

4. Open Floor

Tickets/ PRs

  • @clorith asked if there was an editor lead for 5.9.2? @annezazu will try to follow up.
  • Discussion on @clorith 5.9 regression ticket with some potential solutions (Gutenberg issue 39155). @audrasjb: moved it to 5.9.x todo.
  • @afragen: discussion re: pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party dependencies in the issues https://github.com/WordPress/wp-plugin-dependencies/issues/ Mostly around architecture and design initially.
  • Highlighting PRs from @getdave for anyone who enjoys exploring things early – Slack link.
    Two interesting PRs on the Navigation Menus system to allow menus to be manipulated in isolation from the Navigation block: Dedicated Navigation sidebar.
  • Request from @craigfrancis on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets #52506 and #54042 to get them ready for 6.0, and thanks to @peterwilsoncc for some tweaks on the former
  • Request for anyone able to also test 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. in Trac ticket 42916 ahead of bug scrub on Monday on Quick Edit. 

Gutenberg updates in dev chat

  • @webcommsat: Request to be able to better highlight Gutenberg updates in dev chat in the blog posts or release sections of the meeting? @annezazu: to think through if there could be an async update to share to tie in with the 6.0 update.

Update post dev chat on March 10, 2022:
Light Process for 6.0 Updates for Core Dev Meetings
@annezazu chatted with @priethor and @peterwilsoncc about how best to handle updates for 6.0, partially due to timezone spread. To make things easier, we are going to embrace async updates for the win that can then be shared in the meeting. This matches an approach the Core Editor meeting has taken for project updates. As a result, expect the following:

  • An async thread started each Tuesday (a day before core dev meetings) where release leads can share their updates at some point before the core dev meeting.  @annezazu and @priethor will expect to usually hear from the Core Tech, Core Editor Tech and release coordinator leads but all are welcome to share anything relevant. For core editor, aim to summarize what’s shared earlier in the day for the core editor meeting (example).
  • From there, those updates can be re-shared by @marybaum /@webcommsat during meetings.

Volunteer for dev chat notes

If you could volunteer for dev chat summary in the future, reach out to @marybaum and @audrasjb, the Core Team Reps. It’s a great way to keep up with all the moving parts of a release, and with the things that happen in between!

Props to: @marybaum for the agenda and leading the meeting, and to @webcommsat for co-facilitating and the dev chat summary. Thanks for review by: @marybaum and @annezazu.

#5-9-2-2, #6-0, #dev-chat, #summary

Dev Chat summary, March 2, 2023

Agenda

Start of the meeting on the Make WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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.

1. Announcements

Request: When you bring an issue to Open Floor, it would be great if you also bring a suggestion for a solution.

Our very own Person of WordPress: @hellofromtonya featured in February 2022’s People of WordPress series. Thank you to everyone who contributed. Please share these stories which also encourage existing and new contributors to get more involved and to be inspired by the WordPressers featured.

2. Blogblog (versus network, site) posts of note for core

  • Feedback from the first session of Gutenberg Developer Hours (February 24, 2022)
    • Comments requested by @bph on the proposal on developer.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ and 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/ Developer Hours.
    • Next Gutenberg Developer Hours: Tuesday March 8, 16:00 UTC. Registration link.
  • A feature project around plugin dependencies (February 24, 2022).
    • @afragen: Much of feedback has been in form of questions that I’ve done my best to answer. The biggest is will it be possible to add a non-dot org pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party as a dependency. The answer is that it will be up to lead developers. It could be possible by adding a simple 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. and leaving the heavy lifting to the plugin developer… essentially need lead developer buy-in.
    • encourage further comments and testing of both PRs to see how it might look.
    • @pbiron: I think non-dot-org dependencies are very important use case (e.g., Gravity Forms addons) but also think that it would be fine if they weren’t included in the first version that lands in core

3. Upcoming releases

a) 6.0

WordPress 6.0 development cycle – each major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. has a development cycle section on the Make WordPress core blog.

An addition to the timeline for this release is a walkthrough of the features, on April 5, 2022

Questions in dev chat:

  • is there 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. scrub schedule with 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 a month away?
  • will there be a 6.0 release leads channel?
  • @priethor and @chaion07 any updates you can share in the comments?

b) Next minor: 5.9.2

Last week, it was reported that there were 20 tickets in the milestone.

@audrasjb plans a 5.9.2 bug scrub for March 3, 2022 at 21:00 UTC.

4. Open Floor

@craigfrancis: discussion on how to progress ticket 52506 to add escaping method for table names in SQL queries. More on the discussion in the core Slack.

Component Maintainers – if you think you would like to help manage a component, this refresher gives more information. More maintainers are needed.

Props to: @marybaum for the agenda and leading the meeting, to Mary and @audrasjb for reviewing the notes; and to @webcommsat for the summary of the meeting. Could you help with next week’s notes? Contact team reps @audrasjb and @marybaum

#6-0, #dev-chat, #summary

Dev chat summary, February 23, 2022

@marybaum led the meeting on this agenda from @webcommsat.

1. Welcome and announcements

WordPress 5.9.1 is out! This is a maintenance release that fixed 82 bugs across CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and the 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. editor.

Our 5.9.x minors leads are @audrasjb and @mamaduka. @estelaris is drafting the release posts.

2. Blogblog (versus network, site) posts of note

What’s new in Gutenberg 12.6?

A Week in Core, February 21, 2022

3. Upcoming releases

WordPress 6.0

@afragen asked the group for last-minute feedback on his post that outlines a feature to handle plugin dependencies. The feature is an early 6.0 candidate.

@annezazu caught the group up on a dizzying array of activity around FSE and the block editor. She recommended this summary post from the earlier Core Editor meeting and noted that other work is still following the preliminary roadmap.

See the transcript for more detail.

WordPress 5.9.2

@audrasjb laid out preliminary plans for a quick 5.9.2 to address 20 tickets in the milestone. A firm schedule will come shortly.

4. Open Floor

@bph announced there’s a raw recording of the second Gutenberg Developer Hours on YouTube. She also said a recap post is in the works.

The next session is March 8.

@annezazu announced a call for testing that revisits the headers workflow, which has changed a fair bit since the original call. Note also that her announcement marks the return of the project’s usual calls for testing in the FSE Outreach Program.

@joyously had a concern about the way block themes look in older browsers. @estelaris shared a link to the GitHub Documentation Tracker, where folks can request new support articles.

#6-0, #dev-chat, #summary