[TYPO3-mvc] [RFC] Make 4.7 run with 4.5 LTS?

Jigal van Hemert jigal at xs4all.nl
Sun Feb 12 12:43:06 CET 2012


On 12-2-2012 9:33, Claus Due wrote:
> I think we've taken enough precautions to be able to say that we
> naturally take no responsibility, although we just made it possible,
> when you choose to install development state code on your LTS
> install.
> I can't imagine anybody could rationally assume otherwise?

The general problem is that integrators will not tell their customers 
that they decided to use a new Extbase version on an older TYPO3 core. 
If something goes wrong the customers won't reach the conclusion "my 
integrator messed up with deciding to use this unsupported combination". 
They will only conclude "I have a TYPO3 website and it's broken"; if 
they ask their integrator about it (he's the expert in their eyes) he 
will most likely not admit taking this risk, but will tell the client 
that there is a bug in the core.

It will always be the fault of TYPO3 and never the fault of the integrator.

The point of making 4.5 a LTS version was to have a version which was 
compatible with IE6 (until IE6 was not supported by Microsoft any more). 
The side effect was that there would be a TYPO3 version available for a 
considerable time which was compatible with some older extensions.

If you want to use new features or new extensions which are not 
compatible with 4.5 you need to use a new version of TYPO3.

Building in compatibility with newer, unsupported versions of system 
extensions in older cores will only send the wrong message. No matter 
how much you communicate about it the message will be that the core 
wouldn't have support for a newer Extbase version if it wasn't meant to 
be used together.

Kind regards / met vriendelijke groet,

Jigal van Hemert.

More information about the TYPO3-project-typo3v4mvc mailing list