A WordPress Slack chat exhibits that Matt Mullenweg is contemplating limiting future WordPress releases to only one per yr from now by way of 2027 and insists that the one approach to get Automattic to contribute extra is to strain WP Engine to drop their lawsuit. One WordPress developer who learn that message characterised it as blackmail.
WordPress Core Improvement
Mullenweg’s Automattic already diminished their contributions to core, prompting a WordPress developer attending WordCamp Asia 2025 to plead with Matt Mullenweg to extend Automattic’s contributions to WordPress as a result of his and so many different companies depend upon WordPress. Mullenweg smiled and stated no with out truly saying the phrase no.
Automattic’s January 2025 assertion about lowering contributions:
“…Automattic will scale back its sponsored contributions to the WordPress challenge. This isn’t a step we take flippantly. It’s a second to regroup, rethink, and strategically plan how Automatticians can proceed contributing in ways in which safe the way forward for WordPress for generations to come back. Automatticians who contributed to core will as a substitute deal with for-profit tasks inside Automattic, comparable to WordPress.com, Pressable, WPVIP, Jetpack, and WooCommerce. Members of the “group” have stated that engaged on these kinds of issues ought to depend as a contribution to WordPress.
As a part of this reset, Automattic will match its volunteering pledge with these made by WP Engine and different gamers within the ecosystem, or about 45 hours every week that qualify beneath the 5 For the Future program as benefitting your entire group and never only a single firm. These hours will possible go in direction of safety and significant updates.
We’ve made the choice to reallocate sources as a result of lawsuits from WP Engine. This authorized motion diverts important time and vitality that might in any other case be directed towards supporting WordPress’s progress and well being. We stay hopeful that WP Engine will rethink this authorized assault, permitting us to refocus our efforts on contributions that profit the broader WordPress ecosystem.
WP Engine’s traditionally slim contributions underscore the imbalance that should be addressed for the well being of WordPress. We imagine in equity and shared duty, and we hope this transfer encourages larger participation throughout all organizations that profit from WordPress.”
Slack Submit
The publish on Slack blamed WP Engine for the slowdown and encourages others to place strain on WP Engine to drop the swimsuit.
The next is a quote of Mullenweg’s publish on the WordPress Slack channel, as posted within the Dynamic WordPress Fb Group (should be part of the Fb group to learn the publish) by a dependable supply:
“Wish to put collectively a Zoom for core committers to debate future launch schedule, hopefully bringing collectively a number of the conversations occurring the previous 6 weeks:
6.8 contains a variety of “overhang” contributions from Automatticians, together with 890+ enhancements and bug fixes in Gutenberg.I’d like to verify we get further testing on 6.8 from net hosts, particularly if they will improve maybe their firm blogs or one thing, worker websites, and many others to verify upgrades and all the things work nicely in all environments and with the preferred plugins with out regressions.
The Chromecast replace points right now (https://x.com/james_dunthorne/standing/1898871402049999126 )remind us how simply this may occur.I’m prepared to commit individuals to early roll-out to WP .com to supply widespread testing with tons of of 1000’s of customers. That is very resource-intensive, however has contributed rather a lot to creating positive releases are steady earlier than they deploy to the broader array of non-engaged net hosts up to now.
We must always take into account modifying the discharge schedule:Different company sponsors are protesting WPE’s actions by pulling again contributions, which I feel will impact a number of the different largest contributors after Automattic.
The court docket schedule within the WP Engine lawsuit in opposition to Automattic, me, and WordPress .org ( https://cloudup.com/c33IWQHdNMj ) goes to jury trial in 2027. WPE seems to be unresponsive to public strain to resolve issues earlier. (As I stated at WC Asia, I’m prepared to finish it yesterday.)
We’re approaching 7.0 in two releases, which has an emotional valence and I’d fairly not be purely upkeep. (Nor do I need to break our naming construction and do 6.10.)
One strategy can be delaying 6.8 and making it the one launch this yr, 6.9 in 2026, after which goal for a 7.0 in late 2027 assuming a optimistic end result of the jury trial.FWIW I might estimate WPE is spending the equal of 60 engineers full-time wage at 250k/yr as plaintiffs / attackers, and Automattic an analogous quantity on protection. Think about the challenge may do for democratizing publishing and competing in opposition to proprietary alternate options if that have been going into core and group improvement.
Drop another ideas or agenda objects you’ll have on this thread.”
Response to Mullenweg’s publish:
One Fb person accused Mullenweg of attempting to “blackmail” the WordPress group to strain WP Engine (WPE). They wrote that the group is essentially sympathetic to WPE than to Mullenweg. However normally Mullenweg’s assertion was met with a shrug as a result of they really feel that this may give core contributors the prospect to compensate for sustaining the core which to them is a larger precedence than including extra options to Gutenberg which lots of the builders on this group apparently don’t use.
One lone commenter within the Fb dialogue requested if anybody within the dialogue had made a optimistic contribution to WordPress. On the time of writing, no person had cared to reply.
Featured Picture by Shutterstock/photoschmidt