Mullenweg May Delay WordPress Releases Until 2027

A leaked conversation from a WordPress Slack chat has revealed that Matt Mullenweg is considering slowing down WordPress releases, potentially limiting them to just one per year until late 2027. The discussion has raised concerns within the community about the impact of reduced development pace on the platform’s innovation and stability.

Mullenweg cited a decline in corporate contributions as the primary reason for this potential change. With fewer resources being allocated by major companies, maintaining the current release schedule may become increasingly difficult. This has led to speculation about how WordPress will adapt to these challenges in the coming years.

In the chat, Mullenweg also suggested that increasing contributions from Automattic—his own company—would depend on WP Engine dropping its ongoing lawsuit. This statement has sparked controversy, as it implies that development efforts might be tied to legal disputes rather than the needs of the WordPress community.

One WordPress developer who saw the leaked messages described Mullenweg’s comments as an attempt to exert undue pressure on WP Engine. Some community members have even gone as far as to label the move as a form of blackmail, given the potential consequences for the platform’s development.

The possibility of slowing down WordPress releases has raised concerns among developers, businesses, and website owners who rely on the platform for their online presence. Many worry that a reduced release schedule could lead to delays in security updates, feature enhancements, and performance improvements.

Critics argue that tying contributions to the outcome of a lawsuit undermines the open-source ethos of WordPress. They believe that corporate disputes should not dictate the development timeline of a platform used by millions worldwide.

On the other hand, some supporters of Mullenweg’s stance see it as a necessary step to ensure long-term sustainability. They argue that without adequate corporate support, maintaining the current pace of WordPress updates may not be feasible.

The debate over WordPress release frequency comes at a time when other content management systems are evolving rapidly. Slower updates could put WordPress at a disadvantage compared to competitors that are pushing out new features and improvements more frequently.

As discussions continue, the WordPress community is watching closely to see how this situation unfolds. Whether or not the proposed slowdown happens, it is clear that tensions over corporate contributions and legal battles are influencing the future of the platform.

For now, no official decision has been made, but the leaked conversation has sparked an important conversation about the balance between corporate influence and the open-source nature of WordPress. The coming months will likely determine whether these proposed changes become a reality.

WordPress Core Development

Mullenweg’s Automattic already reduced their contributions to core, prompting a WordPress developer attending WordCamp Asia 2025 to plead with Matt Mullenweg to increase Automattic’s contributions to WordPress because his and so many other businesses depend on WordPress. Mullenweg smiled and said no without actually saying the word no.

Automattic’s January 2025 statement about reducing contributions:

“…Automattic will reduce its sponsored contributions to the WordPress project. This is not a step we take lightly. It is a moment to regroup, rethink, and strategically plan how Automatticians can continue contributing in ways that secure the future of WordPress for generations to come. Automatticians who contributed to core will instead focus on for-profit projects within Automattic, such as WordPress.com, Pressable, WPVIP, Jetpack, and WooCommerce. Members of the “community” have said that working on these sorts of things should count as a contribution to WordPress.

As part of this reset, Automattic will match its volunteering pledge with those made by WP Engine and other players in the ecosystem, or about 45 hours a week that qualify under the Five For the Future program as benefitting the entire community and not just a single company. These hours will likely go towards security and critical updates.

We’ve made the decision to reallocate resources due to the lawsuits from WP Engine. This legal action diverts significant time and energy that could otherwise be directed toward supporting WordPress’s growth and health. We remain hopeful that WP Engine will reconsider this legal attack, allowing us to refocus our efforts on contributions that benefit the broader WordPress ecosystem.

WP Engine’s historically slim contributions underscore the imbalance that must be addressed for the health of WordPress. We believe in fairness and shared responsibility, and we hope this move encourages greater participation across all organizations that benefit from WordPress.”

Leaked Slack Post

In a recent leaked Slack conversation, Matt Mullenweg placed the blame for the potential slowdown in WordPress development on WP Engine. He suggested that members of the community should put pressure on WP Engine to drop its lawsuit, implying that this legal dispute is a major factor affecting WordPress’ release schedule.

The leaked post has sparked significant discussion and concern within the WordPress community. Many developers and users are questioning whether a corporate legal battle should have any bearing on the platform’s development timeline.

A direct quote from Mullenweg’s message on the WordPress Slack channel has surfaced in the Dynamic WordPress Facebook Group. However, access to this post requires joining the group, making it somewhat restricted to the general public.

The message, shared by a reliable source within the group, has drawn mixed reactions. Some believe Mullenweg is being transparent about the challenges WordPress is facing, while others see it as an attempt to shift responsibility for the delays onto WP Engine.

Critics argue that urging community members to pressure a specific company crosses a line, especially when it comes from a key figure in the WordPress ecosystem. They worry that such actions could set a precedent where corporate conflicts interfere with open-source development.

Supporters of Mullenweg’s stance, however, see it as a necessary move to protect WordPress from further instability. They argue that WP Engine’s lawsuit is a direct threat to the broader ecosystem and that resolving the dispute is crucial for WordPress’ future growth.

This development adds to the ongoing debate about the influence of corporate entities on WordPress. With Automattic playing a central role in the platform’s progress, some are questioning whether its business interests are being prioritised over the needs of the broader community.

As discussions unfold, it remains unclear whether Mullenweg’s call to action will have any real impact. WP Engine has not publicly responded to the leaked message, leaving room for speculation about how this situation will progress.

The controversy highlights the growing tension between WordPress’ open-source roots and the increasing corporate influence shaping its direction. Developers and businesses that rely on WordPress will be watching closely to see whether this dispute leads to tangible changes in the platform’s development.

For now, the leaked message serves as a reminder of the complex dynamics at play behind the scenes of one of the world’s most widely used content management systems.

Response to Mullenweg’s leaked post:

In response to Mullenweg’s leaked statement, a Facebook user accused him of attempting to “blackmail” the WordPress community into pressuring WP Engine (WPE). They argued that the broader community appears to be more sympathetic to WPE than to Mullenweg, reflecting a growing divide within WordPress circles.

Despite the strong wording, the general reaction to Mullenweg’s statement was relatively indifferent. Many developers saw the potential delay in releases as an opportunity to focus on maintaining WordPress’ core rather than rushing to add more features to Gutenberg, which, according to discussions in the group, many developers reportedly do not use.

The debate also revealed differing priorities among WordPress contributors. While some see Gutenberg’s expansion as essential to the platform’s future, others believe that stabilising and optimising the existing system should take precedence.

Amidst the back-and-forth discussions, one user posed a thought-provoking question: had anyone in the conversation actually made a meaningful contribution to WordPress? At the time of writing, the question remained unanswered, highlighting a possible disconnect between critics and active contributors.

This ongoing discussion underscores the complex relationship between WordPress’ leadership, corporate entities, and the wider open-source community. With major stakeholders pulling in different directions, the future development of WordPress remains uncertain.