Issue #152 Loop WP

Hi, {{first_name|friend}}. 👋

Welcome to Issue #152 of Loop WP!

Last week, I shared a WooCommerce plugin solution for a client's headache.

This week, we will discuss the result of the March 27th vote on restricting WordPress releases to one yearly release until the WPE lawsuit ends.

😬 WordPress 6.8 has been confirmed as the first and last major release of 2025.

Let’s go! 👇

With Neurons AI, agencies can fast-track everything from creative development to client sign-off.

Neurons AI indicates how campaign assets will perform—before launch—so you can deliver smarter, faster, and with confidence.

Get instant insights on attention, engagement, and memorability, along with AI-powered recommendations to refine assets before clients even see them.

No more endless feedback loops. No more debating design choices. Just clear, data-backed reasoning that helps you present and sell creative work with ease.

Using Neurons AI, Teads helped their client improve brand awareness by 64% and ad recall by 29%.

Get Your Neurons Demo

🚨 If you aren’t aware of the context for this potentially significant meeting for the future of WordPress, then you should read Loop WP, Issue #149 first.

This week’s newsletter will look at the “DotOrg Core Committers Check In” results in isolation and what was confirmed in the context of Matt’s initial proposal.

💡 There’s also a note about WooCommerce at the end of this newsletter.

Mary Hubbard published the outcomes (I encourage you to read this) of the core committers meeting on April 4th, and if you want a super short summary, it would be as follows. 👇

(I’ve added my comments and thoughts in brackets.)

🤔 Gutenberg releases will continue on the current schedule every two weeks (this would suggest to me that, given the limited resources, Gutenberg is the real priority, rather than Core).

✅ To maintain productivity and clear communication, core committers will have quarterly calls on an ongoing basis (I would like to see the minutes for these meetings published).

💡 So, let’s examine things in more detail, considering Matt’s original proposal and what has been confirmed.

We are now looking at one major release per year, which is a significant slowdown in the WordPress release cycle.

All of this is subject to change, but there are currently two key focal areas:

🤔 A slower cycle “can signal an intentional reset and focus on quality”, allowing for larger, more polished releases instead of rapid iterations that risk being “bug-fix only”.

This reinforces what Core committers had been advocating at WordCamp Asia. They discussed how a maintenance-focused approach for the subsequent few releases could be beneficial, given the resource strain.

✅ Minor releases will still occur as needed, and notably, they will have a “more relaxed barrier for inclusion of enhancements” (while avoiding any breaking changes or new files).

💡 That adjustment confirms contributors’ earlier calls to broaden what can be done in minor releases to keep WordPress compatible and evolving during a long gap between majors (for example, accommodating upcoming PHP versions in the interim).

Matt evolved his original proposal by suggesting shifting new feature development out of Core and into “canonical” plugins, which was confirmed in Mary’s announcement.

⚡️ A greater focus on canonical plugins and individual component roadmaps, which can be iterated on and shipped independently of major releases, is not a terrible idea.

This mirrors ideas circulated in earlier conversations (and by Matt Mullenweg in the past) that features can be developed as plugins first, especially when Core is in a holding pattern.

🛠️ The announcement highlights community-maintained plugins as examples of where future feature innovation will live:

This announcement broadly aligns with what had been discussed in late February and March within the WordPress Slack (and contributor discussions at WordCamp Asia), so they won’t surprise many (especially if you read my newsletter, {{first_name|friend}}).

By endorsing “canonical” plugins, it could be argued that the project is confirming a shift in strategy:

Given what has been happening since September, it doesn’t surprise me that we reached this point.

😔 The job losses are very sad, and core contributors are still under strain, and for anyone who’s experienced burnout, you know how tough that can be.

🧠 The statement from Mary Hubbard is arguably a slight change in the narrative, as WP Engine (WPE) and the lawsuit are not mentioned as the reason for this change when they originally were.

💡 However, we can’t escape that reality and the original reasoning behind Matt’s proposal.

As you might know, {{first_name|friend}}, I am heavily invested in eCommerce with WooCommerce, my biggest platform (I am also a Shopify Partner), and I believe the Woo team is in good hands.

🥺 However, with Woo losing over 100 staff members of the 281 that Automattic let go last week, that's a devastating proportion.

I’m particularly concerned that most of the 100 were apparently engineers, and some were seniors, which is not good in the short term (think longer release schedules for Woo).

😬 Now that Automattic has said 6.8 will be the year's first and only major release, how will that impact WooCommerce in the short term?

🫠 If the new major release cycle of one per year for the next couple of years continues, what will that mean for WooCommerce in the longer term?

Will WooCommerce lose significant ground to Shopify and other eCommerce platforms/plugins?

Time will tell…

🚨 The Google Doc contains all the details if you’re interested in sponsoring the Loop WP Newsletter.

⏭️ Next week, I will dig even deeper into Mary Hubbard's announcement (there’s only so much I can fit in one newsletter 🤣) as we look at what has changed since Matt Mullenweg’s original proposal and the potential impact.

(And any community feedback between now and next week.)

In the interim, it’s worth reading The Repository’s article on this topic as Rae offers some additional insights from the community that I don’t cover.

It might also be time to look closely at Webstudio, CraftCMS and others. 😬

See you next week! 😀

This week's excellent and insightful WordPress News & Tips:

If you have a question about this email or WordPress, reply, and I will answer you as soon as possible.

👋 Until next time,