Since the last North American Conference in Québec in Summer many things happened within the TYPO3 Community. A short recap about the things influencing the TYPO3 CMS in the last year and why the development activity dropped to a 6-year-low. It will outline the changes which have been implemented to restructure the core team as well as introduce you to a draft of a vision document the active contributors of the TYPO3 CMS have been working on and which probably will guide our development for the next year. In the end a short look at the short term roadmap - TYPO3 CMS 6.2 LTS - outlining the main goals and time schedule.

1. The future of
TYPO3 CMS

2. Consulting Training
TYPO3-Development
rs systemsweb@
sritterkh
Steffen Ritter

3. What happened since?

4. TYPO3 CMS 6.0
November 2012
TYPO3 CMS 6.1
April 2013

5. photo by www.meteos.de; http://www.flickr.com/photos/internetagentur-mannheim/8060689679/
was born..

6. Rebranding
TYPO3 Products

7. commits over time
source: https://www.ohloh.net/p/typo3

8. Downloads
TYPO3 4.5 TYPO3 4.6 TYPO3 4.7 TYPO3 6.0 TYPO3 6.1
19223263882067915711
54859
19223
158330
268831
298500
1.35 MIO
from SourceForge,
20.05.2013 7:30pm

9. Something had
to change...

10. TYPO3 Core Team
Rest of the world
Core Team Restructuring

11. CMS Team
Active Contributor (“merge“)
All Core Contributors
Core Team Restructuring

13. A clear vision...
• 2006:
Build a new foundation for the future...
• 2008:
„Belin Manifesto“ branches will merge sometime
• 2012:
refined „Berlin Manifesto“ (never published)

14. A clear vision...
• 2006:
Build a new foundation for the future...
• 2008:
„Belin Manifesto“ branches will merge sometime
• 2012:
refined „Berlin Manifesto“ (never published)
Thats NOT a Vision !!!

15. VISION DOCUMENT
//
MIDTERM ROADMAP
DRAFT
https://docs.google.com/document/d/1DEjNmKtMbNrGCzcU3RzcbvF3SbKFs1lNESqAH67s0Sw/edit?usp=sharing

16. TYPO3 CMS is the leading open-source enterprise CMS
by embracing stability, extensibility, and new
technologies from Flow.
It will be superseded by TYPO3 Neos.
„
“

17. vision explained...
• Maintaining a CMS we use now
• Stability and Reliability for TYPO3 LTSVersions
• Licence to Evolve
• TYPO3 CMS needs to converge with TYPO3 Neos/Flow
• Quality Assurance
• No Features / Changes that do not comply with FLOW

18. CMS
Flow
TER TPR
Neos

19. TER
CMS Neos
Flow
Flow
!!!
TPR TPR
Strategy

20. Git submodules
Branching after LTS
Logging
Ease Installation
Finish FAL / Media
PHP versions
MySQLi
Doctrine DBAL vs. adodb DBAL
Don’t delete TCEmain
Functional testing
Performance monitoring
Integrate Flow into TYPO3 CMS
Unified package management
PHP application server
UUID support
Re-invent configuration handling
Scoping and context
Flow object manager and AOP
Usability

21. Git submodules
Branching after LTS
Logging
Ease Installation
Finish FAL / Media
PHP versions
MySQLi
Doctrine DBAL vs. adodb DBAL
Don’t delete TCEmain
Functional testing
Performance monitoring
Integrate Flow into TYPO3 CMS
Unified package management
PHP application server
UUID support
Re-invent configuration handling
Scoping and context
Flow object manager and AOP
Usability

22. TYPO3 CMS 6.2 LTS

23. 2011 April
TYPO3 Release Agenda
TYPO3 4.5 LTS
Main development Regular bugfixes Priority bugfixes & security bugfixes
TYPO3 4.6
TYPO3 4.7
TYPO3 6.0
TYPO3 6.2 LTS
TYPO3 6.1
TYPO3 6.2 + 2
TYPO3 6.2 + 3
TYPO3 6.2 + 1
2011 October 2012 April 2012 October 2013 April 2013 October 2014 April 2014 October 2015 April 2015 October 2016 April 2016 October

24. Main Goals
• Smooth Migration
• User Happiness
• Robust, Stable and Secure Foundation
• Modern Technologies / Interoperability

25. Main Goals
• Smooth Migration
We know about the huge 4.5 LTS user-base. Let those be
able to migrate to the new modern code-base as easy as
possible.
• User Happiness
• Robust, Stable and Secure Foundation
• Modern Technologies / Interoperability

26. Main Goals
• Smooth Migration
• User Happiness
We want to work on the product from the users point of
view (customer, agency, integrator). Making their
experience fun and consistent should guide our efforts.
• Robust, Stable and Secure Foundation
• Modern Technologies / Interoperability

27. Main Goals
• Smooth Migration
• User Happiness
• Robust, Stable and Secure Foundation
The groundwork of TYPO3 should be modern, but still
realistic and timeless.
Let's finish the "last 20%" for important loose ends.
• Modern Technologies / Interoperability

28. Main Goals
• Smooth Migration
• User Happiness
• Robust, Stable and Secure Foundation
• Modern Technologies / Interoperability
We are well aware of what's going on in the PHP world and
Web technologies in general. Keep TYPO3 in sync with
modern technologies, but avoid "experiments" in the LTS.

29. TYPO3 6.2 alpha1
June 4th
January February March April May June July August September October November December
2013
TYPO3 6.2 alpha2
July 6th
TYPO3 6.2 beta1
September 3rd
TYPO3 6.2 beta2
October 1st
TYPO3 6.2 RC1
October 22nd
TYPO3 6.2 Final Release
October 29th
TYPO3 6.2 alpha3
August 6th
Current Release Plan

30. ?