TYPO3 v14 Release Schedule: A Smarter Way Forward

The release cycle for TYPO3 v14 is set — and with it, a new chapter in how we build TYPO3 together. While previous versions were shaped by a fast-paced, multi-sprint cycle, the path for v14 reflects a more focused, collaborative, and flexible approach.

As Feature Unit Roadmap Coordinator, I’ve worked closely with the Core Team, the Product Strategy Group, and the leads of our roadmap objectives to define a release schedule that’s ambitious, yet realistic — structured enough to provide orientation, but flexible enough to reflect the way we currently work.

Embracing Change: Evolving the Release Cycle

We’ve consciously chosen not to tie each sprint release to fixed feature sets. Why? Because TYPO3 is evolving — not just as a codebase, but as a collaborative platform. We want to create space for ideas to mature, for contributors to step in, and to shape the work as it unfolds. That means flexibility, not fixed expectations. 

We’ve also learned from the past that tying sprint releases tied to predefined features created high expectations — often leading to considerable pressure on those responsible, which is difficult to manage in an open source community.

TYPO3 v14 Sprint Releases

Here are the dates for the TYPO3 v14 releases:

• 14.0 – 25 November 2025 – Breaking Changes
• 14.1 – 20 January 2026 – Feature Integration
• 14.2 – 31 March 2026 – Feature Freeze
• 14.3 – 21 April 2026 – LTS Release

Balancing Ambition and Realism

The release schedule reflects both ambition and realism. We’ve seen firsthand that larger features often require structural changes — and with that, more time and flexibility to get things right. By placing the .0 release a bit later than usual, we give ourselves the space to handle those fundamental shifts early on, where they belong. Releasing too early would reduce our flexibility — and in past cycles, this has often meant postponing entire features by a full version.

Of course, a later .0 release gives extension developers slightly less time to adapt their code. That’s a valid concern, but we believe it’s in the best interest of the product overall, allowing cleaner and more future-proof changes to be introduced with enough attention, reducing the risk of multiple follow-up improvements and implementation adaptations. 

Rethinking Collaboration: The Way We Work Has Changed

TYPO3 is currently undergoing one of the most important internal evolutions in years. With the introduction of unit-based team structures, we’re moving away from isolated development tracks, toward integrated, cross-functional collaboration from day one.

Achieving each roadmap objective typically requires collaboration between multiple units. Each objective has a responsible person assigned, and as Unit Roadmap Coordinator for the Feature Unit it is my job to collaborate with them and connect their goals with the teams that will realize them. This includes defining concrete tasks and deliverables, helping with concept validation, and ensuring efforts are aligned and transparent.

The units enable disciplines like UX, development, documentation, and marketing to collaborate throughout the project lifecycle. This avoids situations where documentation or communication become last-minute topics, rushed at the very end of the process.

This change also allows for more flexible and task-specific contributions. Contributors can join specific initiatives without committing to long-term expectations, making it easier to align personal and business goals with TYPO3's broader roadmap. In some cases, it will even be possible to apply for dedicated funding to support work on roadmap objectives.

What's Coming in TYPO3 v14?

We're currently transforming the strategic roadmap goals into clearly defined features. While we won’t make promises we can’t keep, we’re already deep in planning, prototyping, and coordination across multiple teams. Several initiatives are already moving forward as part of the v14 cycle. We are already working on:

• Core migration towards Schema API and Record API
• Dashboard Settings API
• Unified Scheduler Task Registry
• Breadcrumb Component
• Fresh look and feel
• Content Blocks improvements

Other features and concepts are being explored in parallel, each with their own coordination across different teams and units. We’re actively evaluating concepts, preparing prototypes, and keeping room for feedback and iteration.

Get Involved — DevDays and Beyond

A great opportunity to see all of this in action will be at the TYPO3 Developer Days, this August. During the Contribution Night, contributors — new and experienced alike — will be able to join focused initiatives, meet project leads, and directly contribute to the TYPO3 v14 cycle.

Whether you're interested in a particular topic or just want to help fix some bugs, this will be the place to connect and get involved.

Here’s how you can help even beyond the event:

• Fix Core Issues — Every bug you squash helps free up capacity for larger roadmap topics.
• Submit feature requests — Especially if they align with the current roadmap objectives.
• Let us know your availability — Even partial availability helps us plan better. Reach out to me via email or Slack.

I’m excited about what’s ahead, not just because of what TYPO3 v14 will include, but because of how we’re building it: together, transparently, and with focus.

If you have questions, ideas, or want to get involved in any way, feel free to reach out to me directly. I’m happy to help connect you with the right people or opportunities.

See you on the road to v14.