Skip to main navigation Skip to main content Skip to page footer
Newsletter Sign-Up Follow Us
  • Personal Stories & Opinions

Getting TYPO3 v14 Over the Finish Line: Our Week at the Rosenheim Code Sprint

Several people work on computers at a large table in an office. Some are seated, focused on their monitors, while one person stands nearby. Coats, backpacks, and documents are visible in the casual, collaborative workspace.

With a clear mission to complete outstanding v14 tasks, Marno shares the highlights from our team sprint in Rosenheim, Germany, where collaboration and focused effort brought us closer to the final release.

  • Marno Schmigotzki

2–6 February, 2026, the TYPO3 community came together in Rosenheim, Germany, for a focused code sprint hosted at in2code GmbH in the historic Kunstmühle. Unlike earlier v14 sprints that explored and validated new ideas, this week was explicitly about the last mile: finalization, revision, and completion of features already started before the feature freeze for TYPO3 v14 on 31 March.

Why This Sprint Mattered

TYPO3 v14 is a major step in backend modernization, developer experience, and long-term maintainability. The Rosenheim sprint was scheduled at the perfect moment: close enough to the freeze to optimize, review, and merge work that has already been started.

The agenda matched that focus. The sprint concentrated on:

  • UX and backend modernization
  • Themes
  • Integration & Exchange APIs
  • Final implementation work on new v14 APIs
A group of nine people, featuring both men and women, stands smiling in an office room. There are certificates on the left wall, and a large window with blinds and a poster behind them.

Our Goal During the Week

Our goal as a community was simple: turn open changes into finished contributions. We approached this in three main ways and jumped in wherever help was needed most.

1) Finishing Almost Ready Work

Sprints are great for getting half-finished changes over the line. On site, we could quickly sync up, clear up open questions, and turn nearly done into done.

2) Fast Reviews and Unblocking Each Other

We didn't just code, we also reviewed and discussed. Being together meant shorter feedback loops: instead of comment changes, we could talk for a few minutes and keep moving. In my opinion, that was one of the biggest advantages of the sprint.

3) Checking Quality and Real-World Behavior

We also took time to make sure everything worked well in practice: testing flows, catching small issues, and smoothing out rough edges before the freeze.

A round table with bowls of snacks, bags of candy, a bottle of water, bananas, and packaged treats, set in front of an orange wall with the TYPO3 logo.

A Sprint Rhythm That Works

The Rosenheim sprint was designed to keep the flow going: a clear scope (finish what’s started), a focused group of participants, and short daily syncs to catch blockers early. The event itself focused on practical collaboration, with core developers providing architectural direction and reviews, allowing work to proceed from idea → patch → feedback → merge in tight loops.

That's why sprints work so well: we don't just create commits, we also establish a common understanding, which continues to be beneficial even after the sprint is over.

Bowling Night at Halfway Point

On Wednesday evening, midway through the sprint, we took a break from coding and went bowling. It was a great chance to get to know each other better and exchange ideas in a more relaxed setting. in2code kindly hosted the evening, making it even more special.

Two people are bowling in a brightly lit bowling alley with colorful murals on the back wall. One is about to release a green bowling ball, and the other has just thrown their ball down the lane.
A group of people at a bowling alley, some sitting and some standing, watch as a man prepares to bowl. Bowling balls are on the rack and colorful decorations hang above the lanes.

A Few New Starts That Still Fit the Goal

Even though our main focus was “finish what’s started,” the sprint agenda also included a few new items, mainly where it made sense to begin the work together and get the basics in place early. That’s how we started things like a Short URL module and the use of a password generator in several spots. These improvements are already in progress, and we’d like to have them merged before the feature freeze.

The Place: Kunstmühle, Alps, and a Very TYPO3 Atmosphere

in2code hosted the sprint in Rosenheim, at the historic Kunstmühle. The venue was an inspiring blend of industrial character, riverside calm, and easy access to fresh air which was perfect for quick mental resets between intense coding sessions. Inside, we could dive deep into problem-solving, while short breaks outside kept energy and focus high. It was the ideal setting to collaborate, make progress, and fully immerse ourselves in TYPO3 v14.

A tall white building with red-trimmed windows and a tower stands beside a row of parked cars on a cobblestone street, with two people walking on the sidewalk under a partly cloudy sky.
in2code hosted the sprint in Rosenheim, at the historic Kunstmühle. Completed in 1916, the old grain silo's 54 meter-tower is landmark of Rosenheim.

What We Took Away

Beyond the progress we made in code, the week taught us a few important lessons:

  • Finishing beats starting new things: Focusing on completing and polishing work helped us make real progress.
  • Quick feedback makes a huge difference: Being on site sped up reviews and reduced rework.
  • The community is what makes TYPO3 thrive: Progress happens because people show up, share knowledge, and take care of the details.

Personally, my biggest takeaway from the week was how much easier contributing becomes when working side by side in real time. Meeting in person made a real difference: It was inspiring to see everyone collaborate side by side, sharing knowledge, offering help, and tackling tricky tasks together.

Sprint Output

We made great progress as a team, and it feels rewarding to look back on what we accomplished this week: We merged ~30 patches, submitted ~80 patches, and did many, many reviews.

An achievement we can be really proud of!

But we are not done yet! Everyone is invited to help us integrate as many patches as possible into TYPO3 v14.

Several people sit at computer desks working on desktop monitors in a modern office with exposed wooden beams. Two others stand nearby. A foosball table is in the foreground and shelves and a whiteboard are in the background.

Thanks

A huge thanks to in2code GmbH for hosting the sprint in Rosenheim and for taking such great care of everyone throughout the week.

The venue, the organization, and the overall atmosphere made it incredibly easy to stay focused, productive, and have fun along the way.

And a special shout-out goes to our mentors Oli Bartsch, Oliver Hader and Benni Mack (and of course all the Core contributors). Your guidance, quick feedback, and steady hands-on reviews kept us moving forward and helped turn a lot of sprint energy into real progress for TYPO3 v14.