[TYPO3-core] Deprecation strategy

[Susanne Moog]

Hey

On 07/10/2012 04:14 PM, Benjamin Mack wrote:
> Hey all,
> 
> the problem is that any extension owner who wants to use readLLXMLfile
> and/or intInRange and keep their extension compatible with 4.5 and 6.0
> has a real big problem, and needs to some kind of
> backwards-compatibility layer that he/she will create on his own in each
> extension.
> 
> For my extensions, I will need to maintain two versions, which sucks big
> time.

Maintaining two versions of an extension for different versions of the
underlying system would be no problem (and we are in fact doing that for
a lot of our internal libraries etc as for example extbase changed a lot
between 4.5 and now). A clean API for it would ease that even more (like
EM and TER able to distinguish different extension major versions for
different TYPO3 versions, being able to upload different branches
without problems)... For me those are pretty bad circumstances
considering but should not impact the deprecation strategy.

just imho ;)

susi


-- 
Susanne Moog
TYPO3 Core Team Member

TYPO3 .... inspiring people to share!
Get involved: http://typo3.org