WordPress has long been the backbone of the open web - powering over 40% of all websites and supported by a vast, mostly volunteer-driven contributor network. But that momentum may be faltering. Recent discussions among WordPress project leaders reveal a growing concern: a significant reduction in organizational support for core contributions is stalling development, prompting strategic changes that could reshape the platform’s future.
One Major Release in 2025 - Then What?
During a recent leadership meeting, it was decided that WordPress 6.8 will be the final major release of 2025. Beyond that, there are no concrete commitments to future major releases - a decision that has raised eyebrows and led to speculation about a slowed release cadence becoming the new normal.
Although not explicitly stated, the tone of the conversation strongly suggested that WordPress may shift to just one major release per year if current contributor levels remain this low. This ambiguity prompted contributors to seek clarity, with one commenting:
“Is the new release cadence one major release a year now, or is that just for this year? If getting users to wait a year for major updates, can I suggest some work towards an open roadmap… where resources are limited, [users could] vote on said features to help prioritize what the community wants from WordPress?”
This idea - greater transparency through roadmaps and more user input on feature development - highlights an underlying tension between user expectations and what the current contributor ecosystem can realistically deliver.
Stalled Progress: Gutenberg and Core Tickets Stagnant
Another red flag? Ticket activity on both the Gutenberg and Core Trac repositories has remained flat for six months. In open-source development, a stagnant ticket queue often means unresolved issues are piling up while new ideas stall out.
Specifically, Gutenberg feature development has noticeably slowed since January, with fewer new blocks, interface improvements, or experimental features being rolled out. This lack of innovation threatens the long-term goals of the block editor project, which is central to WordPress’s future vision.
If Gutenberg stalls, so does much of the future promise of WordPress as a more modern, intuitive content management system.
A Silver Lining? Time for Automation and Infrastructure
The slowdown isn’t entirely bleak. With fewer major features in the pipeline, some of the freed-up time is being used to focus on release automation. While the term was used vaguely during discussions, the idea is to reduce the manual effort involved in packaging and shipping updates.
Documentation suggests that streamlining the release process could help WordPress move faster in the future - once more contributors return or once additional automation is in place:
“Allows for work to further automate release processes, making future releases quicker and less manual.”
It’s a pragmatic pivot: when human power is limited, automation becomes not just helpful, but essential.
Canonical Plugins Take Center Stage - But Where’s the Buzz?
With core development lagging, WordPress is also doubling down on its “canonical plugins” strategy - officially maintained plugins developed to serve as extensions of core features. Think of them as a bridge between core development and third-party plugin ecosystems.
Currently, the focus is on a few key plugins, including:
- Preferred Languages
- Two-Factor Authentication (2FA)
- Performance Tools
These plugins are meant to function like mini-core modules - maintained by the project, recommended for wide use, and held to high standards. However, two major challenges remain:
- Lack of User Feedback
Active install counts are the only widespread metric available, but they’re a poor substitute for understanding how users actually interact with these plugins. Feedback usually only appears when something breaks - hardly ideal. - Low Awareness
Even among seasoned developers, awareness of canonical plugins is minimal. There’s no centralized place to view or explore them, and they’re rarely mentioned in documentation or official communication.
A contributor commented:
“As a developer and WordPress professional, [canonical plugins] are rarely on my radar until I stumble upon them… Is there even a link to them in the repository where we can view them all?”
Clearly, for canonical plugins to succeed, the project needs to not only build them - but also communicate their existence and value.
Backlog Blues: 13,000+ Open Tickets
Adding to the concerns is the massive backlog of unresolved issues - around 13,000 tickets remain open across the Core and Gutenberg repositories. While minor core releases will continue throughout the year to address bugs, this enormous queue represents both technical debt and missed opportunities.
There’s also concern that the project may be slowly burning out its contributor base without replenishment. Without broader organizational support or new contributors entering the ecosystem, progress will remain uneven at best.
The Road Ahead: Slower, Smaller, and More Strategic?
Here’s what’s been officially decided:
- WordPress 6.8 will be the final major release of 2025.
- Minor releases will continue as needed (primarily bug fixes, with no new files).
- Gutenberg plugin updates will still ship every two weeks.
- Quarterly contributor strategy calls will begin to maintain open dialogue and adapt as necessary.
But the real takeaway is this: WordPress is in a moment of recalibration. It’s not collapsing, but it is adjusting. The reliance on volunteer and sponsored contributors has long been both a strength and a vulnerability - and now that ecosystem is being tested.
This may be the perfect time for WordPress to revisit its organizational model, communication strategies, and perhaps even consider introducing more direct ways for users to support core development - whether through funding, feedback, or better community structures.
For now, users and developers should temper expectations, stay engaged, and keep an eye on how the project evolves through what feels like a defining transitional period.
