<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[WP23]]></title><description><![CDATA[<blockquote>
<p dir="auto">Last week, we shipped WordPress 7 to the world. In seven days, 46% of all WordPresses, tens of millions across countless different hosting environments, are already on 7.0, auto-updated with no breakage. From a Raspberry Pi to the most secure sites in the world, like <a href="http://WhiteHouse.gov" rel="nofollow ugc">WhiteHouse.gov</a>. Sit with that for a minute when you think of all the resources and all the projects that have had security problems in the past few weeks. No supply chain attacks, no security problems, just a stable, secure infrastructure doing its job invisibly to power a huge portion of the open internet. However, the release was not what I hoped it would be because so much time from key people was taken away by WP Engine’s attacks.</p>
</blockquote>
<ul>
<li><a href="https://wordpress.org/news/2026/05/wp23/" rel="nofollow ugc">https://wordpress.org/news/2026/05/wp23/</a></li>
</ul>
]]></description><link>https://billboard.bsd.cafe/topic/211/wp23</link><generator>RSS for Node</generator><lastBuildDate>Thu, 25 Jun 2026 03:18:13 GMT</lastBuildDate><atom:link href="https://billboard.bsd.cafe/topic/211.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 29 May 2026 11:56:17 GMT</pubDate><ttl>60</ttl></channel></rss>