[TYPO3-team-core-v5] Project Structure on forge

Tim Eilers tim.eilers at web.de
Fri May 2 17:44:43 CEST 2008


Sebastian Kurfuerst schrieb:

> 
> I'm curious for your input :-)
> 

Perhaps i am not the best to say anything to that, since i didn't ever 
wrote something for typo3 v4 and am very new to it, but i have some 
things to mention about your suggestion:

Your idea to seperate the two TYPO3 versions is a good idea, but 
logically not the best: If its ordered like this, one could think, that 
TYPO3 v5 is the basis for FLOW3. But as we all know its vice versa. I 
would simply exchange the main point "TYPO3 v5" with "FLOW3". The point 
"TYPO3 v5 R&D" could stay there, since it will be a part of FLOW3.

Later, when FLOW3 is somehow finished, there will be the main work on 
TYPO3 v5. Then you could make it an extra own main point. Imagine, that 
in the future there could be packages for FLOW3 (f.e. flow3cgl) and 
packages that only run with TYPO3 v5 (-> extensions).

And i would move "TER" to "TYPO3 v4", cause the v5 TER will somehow be 
covered by the package manager (or however that part is called *G*) and 
perhaps not called TER.

Cheers, Tim.


More information about the TYPO3-team-core-v5 mailing list