[TYPO3-core] [TYPO3-core-internal] Deprecation strategy

Christian Kuhn lolli at schwarzbu.ch
Wed Jul 11 22:48:15 CEST 2012


On 07/11/2012 10:33 PM, Jigal van Hemert wrote:
> If you want to support older versions (I can't imagine why, but that's a
> different story) that's fine as long as the range includes supported
> versions of the core:
> - 4.2.0-4.4.99 => wrong
> - 4.3.1-4.6.99 => correct

The important point is that the em must support branches properly, and 
probably the TER display must be tuned here as well:

Currently em will by default only choose the latest version of an extension.

It would be great, if an ext author could for example maintain branch 
1.0.x of an extension supporting 4.5 and 4.6, and a different branch 
with version 1.1.x supporting 4.7 and 6.0.

The em then must only chose the 'fitting' branch: On a 4.5 instance it 
should choose 1.0, on 4.7 it would display 1.1.x as installable / 
ugradable version.
Other package systems can do exacly this (For example in firefox it is 
not possible to install the latest version of firebug, if firefox is too 
old, a different version tree is chosen then).


More information about the TYPO3-team-core mailing list