Outreach to component maintainers 6.2

[bph]

Outreach to component maintainers for Field Guide "But Wait, There is More!" section (WordPress 6.1)

Reference in release documentation

[Publishing Field Guide](https://make.wordpress.org/core/handbook/tutorials/publishing-the-field-guide/) "Each Component team is sent a group direct message in Slack, pulling the list of maintainers from the [individual component pages](https://make.wordpress.org/core/components/)"

Example message:
It’s that time again Component Name component maintainer(s)… are there any tickets in the 6.0 release that you’d like called out in the Field Guide that aren’t already included in a Dev Note? As a reference, here are the ## tickets currently in the milestone for you: https://core.trac.wordpress.org/query?component=`ComponentName`&-milestone=6.1&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=priority. Note that we intend to publish the Field Guide next week, so the sooner you can respond the better… thanks!

List of components

• The link goes to the list of tickets for the milestone for the component. The number of tickets is in parentheses.
• A blue check mark means maintainers were contacted or no issues.

---

• Administration (11)
• Bootstrap/Load (0)
• Build/Test Tools (33) ✅
• Bundled Theme (58) ✅
• Cache API (0)
• Comments (7) ✅
• -- Pings/Trackbacks (2)
• Cron API (0)
• Customize(5) 🦗
• Database (2) ✅
• Date/Time(2) 🦗
• Editor(48) also shared [Gutenberg Dev Note tracking issue] 🦗(6.2 Dev Note Tracking Issue gutenberg#47771)
• -- Autosave (0)
• -- Quick/Bulk Edit(1)
• -- TinyMCE (0)
• Export (0)
• External Libraries(8) ✅
• Feeds(1) 🦗
• Filesytems API (4) ✅
• Formatting(10) ✅
• -- Charset (0)
• -- Emoji (2) ✅
• -- Shortcodes (0)
• General(35) ✅
• Help/About Page(8)
• HTTP API(5) 🦗
• i18n(7) ✅
• Import (0)
• Mail (3)
• Media(28) ✅
• -- Embeds (3)
• -- Gallery (0)
• -- Upload (0)
• Network/Sites(6) ✅🦗
• Options/Meta APIs (4) ✅
• Permalinks(3) 🦗
• -- Canonical (1) (sub component) 🦗
• -- Rewrite Rules (0) (sub component)
• Plugins (5)
• Posts, Post Types (11)
• -- Post Formats (0)
• -- Post Thumbnails (0)
• -- Revisions (4) 🦗
• Privacy(1) 🦗
• Query (3) 🦗
• REST API (4) ✅
• [x]Application Passwords (1) ✅
• Script Loader (0)
• Security (4)
• Site Health (3) ✅
• Sitemaps (0)
• Taxonomy (7) 🦗
• Themes (19) 🦗
• -- Menus (4) ✅
• -- Widgets (2) ✅
• Toolbar (1)✅
• Upgrade/Install (11) ✅
• Users (7)
• -- Login & Registration (5)
• -- Role/Capability (0)
• XML-RPC (1) (0)

---

Note to future self:
I used this Google Sheet to get the message for each component and the link to the tickets, just replace in the message 6.1 with 6.2 in the WP version column.

[zzap]

Heads up @WordPress/docs-issues-coordinators, we have a new issue open. Time to use 'em labels.

[bph]

These 48 tickets for inclusion into the Fieldguide, or Miscellaneous dev note or a single stand-alone dev note post. The tickets are from components without maintainers.

• Administration (11)
• Pings/Trackbacks (2)
• Mail (3)
• Plugins (5)
• Posts, Post Types (11)
• Security (4)
• Users (7)
• Login & Registration (5)

[carolinan]

For review

Bundled Themes
Twenty Twelve to Twenty Seventeen now includes font files in the theme folder instead of loading fonts from a remote source (Google Fonts). This update ensures that the themes follow current recommendations for fonts from a privacy perspective.

[bph]

for External libraries:

The following libraries were updated to the latest versions:

• jQuery (#57324)
• jQuery Migrate (#56743)
• PHPMailer (#57281)
• element-closest (#52851)
• regenerator runtime (#57646)
• polyfill-library (#57646)
• Requests 2.0 (#54504) Read through Request 2.0 docs.

[bph]

Filesystems API (by Colin Stewart @costdev)

Function changes

WP_Filesystem_Direct::move()
In #57375 WP_Filesystem_Direct::move() had directory support added to make it consistent with ::move() methods in WP_Filesystem_FTPext, WP_Filesystem_ftpsockets and WP_Filesystem_SSH2.

New functions

wp_opcache_invalidate_directory()
wp_opcache_invalidate() invalidates the OPcache for individual PHP files after overwriting. In #57375 wp_opcache_invalidate_directory() was added to recursively invalidate the OPcache for PHP files after overwriting. The function accepts a single argument, (string) $dir, pointing to the directory containing PHP files for which OPcache is to be invalidated.

[bph]

@zzap for three components, we have content for the field guide. see comments above ^^

[zzap]

thank you @bph

[zzap]

All these are added to the field guide.

[bph]

Oops,.should have closed it with the 6.2 release