<div style="text-align:center"></div><div>
<p>The full chat log is available beginning <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1741708859096019">here on Slack</a>.</p>
<h2 class="wp-block-heading"><strong>WordPress Performance Trac tickets</strong></h2>
<ul class="wp-block-list">
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> The <a href="https://wordpress.org/news/2025/03/wordpress-6-8-beta-2/">second beta of 6.8</a> was just released.</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> There are <a href="https://core.trac.wordpress.org/query?status=accepted&#038;status=assigned&#038;status=new&#038;status=reopened&#038;status=reviewing&#038;focuses=~performance&#038;milestone=6.8&#038;col=id&#038;col=summary&#038;col=status&#038;col=owner&#038;col=type&#038;col=priority&#038;col=milestone&#038;order=priority">5 performance tickets in the milestone</a>.
<ul class="wp-block-list">
<li><a href="https://profiles.wordpress.org/johnbillion/" class="mention"><span class="mentions-prefix">@</span>johnbillion</a> RE <a href="https://core.trac.wordpress.org/ticket/63026">#63026</a>, this is an issue with the performance of the tests due to the high number of user fixtures, all of which generate and hash a password for the user with each fixture. The regular performance tests are not indicatiny any general performance regression. I think we can therefore remove the <code>performance</code> focus unless there’s an objection.</li>
</ul>
</li>
</ul>
<h2 class="wp-block-heading">Performance Lab plugins</h2>
<p>Discussing the upcoming release scheduled for <strong><a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20250317T1700"><abbr class="date" title="2025-03-17T17:00:00+00:00">Monday, Mar 17, 2025 at 17:00 UTC</abbr></a></strong>.</p>
<ul class="wp-block-list">
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> Let’s start with the upcoming set of Performance Lab releases which is due March 17th.</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> As <a href="https://github.com/WordPress/performance/issues/1853#issuecomment-2711374560">noted</a> by <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>, this release won’t actually include any update to the Performance Lab plugin itself. Instead there will be updates to Optimization Detective, Image Prioritizer, Embed Optimizer, Speculative Loading, and Modern Image Formats. Therefore, he suggests that we take this as an opportunity move away from using the PL’s version for the release tags. In reality this should have been done long ago when we split up the plugin into standalone plugins. So instead of the release branch being <code>release/4.0.0</code> it could instead be <code>release/20250317</code>. The title of the release then I suppose would be <code>2025-03-17</code> as well.</li>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> Does the release triggered manually as we didn’t release PL plugin?
<ul class="wp-block-list">
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> The GHA workflow doesn’t depend on releasing the PL plugin anymore, right? I mean, ever since the plugin was split into standalone plugins, I don’t think this was the case</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> It would feel a bit odd to have a release called 2025-03-17 in the GitHub releases page, but I’d argue that’s only because of the previous releases using the PL version number. It’s already odd now in that each release is labelled by the PL version number, but actually includes multiple releases using different versions. So I think that would be fine.</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> We can include a note in the release description that explains the naming convention change.</li>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> What happens in the future if we find ourselves in the same situation? Will we use the release date again?</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> Yeah, I think we’ll use dates from now on.
<ul class="wp-block-list">
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> Are you saying we should use dates for the release branches and GH releases going forward even when PL is among the released plugins? If we are going to do that, we should modify the documentation in the Core Performance Handbook.</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> Yes, I think we should use dates going forward.</li>
<li><a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> Agreed. Would be even more confusing otherwise.</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> There are 4 <a href="https://github.com/WordPress/performance/milestones?direction=asc&#038;sort=due_date&#038;state=open">milestones</a> for Monday which have issues/PRs:
<ul class="wp-block-list">
<li><a href="https://github.com/WordPress/performance/milestone/104">speculation-rules 1.5.0</a></li>
<li><a href="https://github.com/WordPress/performance/milestone/105">webp-uploads 2.5.1</a></li>
<li><a href="https://github.com/WordPress/performance/milestone/106">embed-optimizer 1.0.0-beta2</a></li>
<li><a href="https://github.com/WordPress/performance/milestone/107">optimization-detective 1.0.0-beta3</a></li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> Looks like Modern Image Formats primarily just needs a couple tweaks prior to merging <a href="https://github.com/WordPress/performance/pull/1885">one PR</a>. It looks like the <a href="https://github.com/WordPress/performance/pull/1868">other PR</a> will need to get bumped.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> Regarding the changed branch naming and release naming strategy, anyone up for updating the Make Core <a href="https://make.wordpress.org/performance/handbook/performance-lab/releasing-the-plugin/">Performance Handbook documentation</a> accordingly?
<ul class="wp-block-list">
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> I can do it. I typically tweak the handbook after going through the release based on how it went.</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> I have to share update on the accurate sizes project: I picked it up and started working on it this week. The PR <a href="https://core.trac.wordpress.org/ticket/1795">#1795</a> adds the ancestor block context and is ready for review.</li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20250325T1600"><abbr class="date" title="2025-03-25T16:00:00+00:00">Tuesday, Mar 25, 2025 at 16:00 UTC</abbr></a> in the <a href="https://wordpress.slack.com/messages/core-performance/">#core-performance channel</a> in <a href="https://make.wordpress.org/chat/">Slack</a></strong>.</p>
<p class="o2-appended-tags"><a href="https://make.wordpress.org/core/tag/core-performance/" class="tag"><span class="tag-prefix">#</span>core-performance</a>, <a href="https://make.wordpress.org/core/tag/hosting/" class="tag"><span class="tag-prefix">#</span>hosting</a>, <a href="https://make.wordpress.org/core/tag/performance/" class="tag"><span class="tag-prefix">#</span>performance</a>, <a href="https://make.wordpress.org/core/tag/performance-chat/" class="tag"><span class="tag-prefix">#</span>performance-chat</a>, <a href="https://make.wordpress.org/core/tag/summary/" class="tag"><span class="tag-prefix">#</span>summary</a></p>
</div>

Cloudways is bringing back its free Prepathon online event next week, from September 30 to…
Fueled has confirmed layoffs this week, cutting 4–5% of its workforce. But the news reached…
After calling for “more weirdness” in WordPress theme design earlier this year, Nick Hamze has…
FAIR has reached its first major milestone with the release of version 1.0 this week,…
The full chat log is available beginning here on Slack. WordPress Performance Trac tickets @westonruter…
Back in 2011, Jon Penland was selling centrifugal pumping units into the water and wastewater…