FLOW3 1.1 beta 2 released
The FLOW3 team is pleased to announce the release of FLOW3 1.1 beta 2. About two weeks after the release of the first beta, we have now all features for FLOW3 1.1 in place and present this second beta for getting feedback from the FLOW3 community.
Read moreWhat about T3CON12 in Québec, Canada?
Preparing for this article, I asked Patrick Gaumond, conference organizer: "What will T3CON12 Canada be like?" He answered: "It will be fantastic!" Let's have a closer look.
TYPO3 6.0 alpha1 released
The TYPO3 Core Development Team and the TYPO3 Community is proud to present a sneak preview of the next TYPO3 Version 6.0
TYPO3 Community April 2012
The relaunch of typo3.org kicked of the month of April. The seventh edition of the TYPO3 Developer Days took place from April 12 - 15, 2012 at MACE, Unterföhring near Munich, Germany and the month closed with the release of TYPO3 version 4.7 on April 24.
TYPO3 4.5.16, 4.6.9 and 4.7.1 released
The TYPO3 Community announces versions 4.5.16, 4.6.9 and 4.7.1 of the TYPO3 Enterprise Content Management System.
TYPO3 Association set-up meeting
The members of the different bodies (Board, BCC and EAB) of the TYPO3 Association met on March 19 and March 20 in Düsseldorf to initiate the new TYPO3 Association structure.
TYPO3 6.0 Release Timeline
As already announced, the release of TYPO3 6.0 will be this fall. To be precise: We scheduled the final release to be on 27th of October this year.
FLOW3 1.1 beta 1 released
The FLOW3 team is pleased to announce the release of FLOW3 1.1 beta 1. After several months of development, we have now closed the lid of the feature box and present this first beta for getting feedback from the FLOW3 community.
TYPO3 6.0 - Back to the Future
Back on track, embracing the Future. Our ideas for the upcoming TYPO3 6.0 release.
TYPO3 Phoenix and FLOW3 - April 2012
The major event for the TYPO3 community in April surely were the TYPO3 Developer Days in Munich. We had handed in a number of session and workshop proposals centered around Phoenix and FLOW3 - and were overwhelmed by the response we had. Afterwards the focus of a part of the team went back to FLOW3, to get things done for the release of version 1.1.