Outreach to component maintainers WP 6.1

[bph]

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

Publishing Field Guide
"Each Component team is sent a group direct message in Slack, pulling the list of maintainers from the individual component pages"

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 (17)
• Bootstrap/Load (4)
• Build/Test Tools (41)
• Bundled Theme (58)
• Cache API (3)
• Comments (6)
• -- Pings/Trackbacks (1)
• Cron API (4)
• Customize(7)
• Database (11)
• Date/Time(2)
• Editor(13) also shared Gutenberg Dev Note tracking issue
• -- Autosave (1)
• -- Quick/Bulk Edit(5)
• -- TinyMCE (0)
• Export (0)
• External Libraries(11)
• Feeds(2)
• Filesytems API (3)
• Formatting(14)
• -- Charset (0)
• -- Emoji (1)
• -- Shortcodes (0)
• General(23)
• Help/About Page(4)
• HTTP API(3)
• i18n(13)
• Import (0)
• Mail (1)
• Media(28)
• -- Embeds (1)
• -- Gallery (4)
• -- Upload (0)
• Network/Sites(7)
• Options/Meta APIs (4)
• Permalinks(8)
• -- Canonical (0) (sub component)
• -- Rewrite Rules (7) (sub component)
• Plugins (7)
• Posts, Post Types (18)
• -- Post Formats (0)
• -- Post Thumbnails (0)
• -- Revisions (0)
• Privacy(0)
• Query (11)
• REST API (10)
• Application Passwords (4)
• Script Loader (4)
• Security (4)
• Site Health (12)
• Sitemaps (2)
• Taxonomy (11)
• Themes (12)
• -- Menus (3)
• -- Widgets (3)
• Toolbar (2)
• Upgrade/Install (17)
• Users (9)
• -- Login & Registration (6)
• -- Role/Capability (1)
• XML-RPC (1)

_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 Text and the WP version column. _

[bph]

Cron Component

Add error logging and hooks to wp-cron.php

In #56048 error logging was added to WP-Cron to indicate when an event fails to get rescheduled or unscheduled. The actions cron_reschedule_event_error and cron_unschedule_event_error have been introduced to allow developers to run custom tracking on these errors.

Non blocking wp-cron.php with LSAPI

In #54668 requests to wp-cron.php were made non-blocking for the LSAPI PHP implementation. Network requests for wp-cron.php will close prior to the processing of events inline with the behaviour for sites using PHP FPM.

Props to Peter Wilson and John Blackbourn

[bph]

Network/Sites component - Jonny Harris is working directly with Milana.

[bph]

Embeds Component:

#55771 Support for Google Data Studio
#55860 Pocket Casts as an oEmbed provider
#56733 Tumblr reader URLs

[bph]

Double-checked responses from component maintainers I updated the "But Wait" section of the field guide:

• Maria DB minimup requirement
• link preload
• Embeds oEmbed

Added Cron Component information to the Misc Post

This tracking issue is all done.