7.0.2 security release; 7.1 beta 3 due
Start of the meeting in Slack, facilitated by @audrasjb 
See the agenda post.
Announcements 
7.0.2
7.1
- 7.1 beta 3 is due for release tomorrow (Wednesday, July 22). The release party starts at 15:00 UTC.
Note: beta 2 was released on Friday with the above security fixes. - We have a heads up from @adrianduffell:
- There’s about 140 Trac tickets milestoned for 7.1. It would be good for owners to start punting the tickets that can be safely picked up in a future release. This will help to make the remaining 7.1 priorities clearer.
- Adrian wanted to highlight a few bugs with simple PRs needing review. It might be possible to merge them before beta 4 next week:
- Some additional info shared by @wildworks:
- Aki will be starting the Gutenberg 23.6 release process around 9:00 UTC tomorrow.
- Once that is complete, Aki will sync core and Gutenberg for Beta3.
- The commit freeze is scheduled for 14:00 UTC tomorrow. See this Slack thread for more info.
General
- Performance Chat Summary: 14 July 2026
- In case you plan to go to Phoenix, there’s a Guide to WCUS 2026
Discussion 
From @joedolson
Joe expects to land ticket #50921 later today, and will probably want a final review of that at some point.
The goal is to ensure that the related API is as mature as possible, so I’m going to implement the mechanics @afercia describes for links, but not the implementations; that will go into a separate ticket. Noting that the API is already committed and has needs-dev-note workflow keyword ; this ticket is for the metaboxes. Joe won’t add the implementation for the media library icons as suggested in the current PR, though.
From @jonsurrell
Jon hopes to land some improvements to the documentation site for 7.1. @dmsnell and Jon collaborated during 7.0 fix and update the documentation parsing. Jon hopes to get those changes landed for the parser soon so its in a better state. More recently, @zieladam and him have been looking at interactive, runnable code examples in the documentation for Core. The Playground docs have this already, see this example. Those snippets are powered by Playground.
Right now, code snippets are typically done by using extra indentation in the phpdoc. What Adam and I have discussed is not to simply upgrade all the example code to these runnable snippets, but to require an opt-in style where we’d use php codefences like (slack markdown will mangle this):
```php interactive
<?php echo "example";
```These changes happen across https://github.com/WordPress/phpdoc-parser/pull/258 (parse the new interactive snippets) and https://github.com/WordPress/wporg-developer/pull/567 (render the interactive snippets in the developer docs).
For example, consider this page which has this snippet:
$p = WP_HTML_Processor::create_fragment( "<div class='free <egg<\tlang-en'>" );
$p->next_tag();
foreach ( $p->class_list() as $class_name ) {
echo "{$class_name} ";
}
// Outputs: "free <egg> lang-en "The idea is to just change that to be interactive. It’s extracted with the rest of the documentation and is rendered in a runnable snippet. The runner is entirely handled by playground.
Fetched July 22, 2026
