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

[Ingmar Schlecht]

Hi guys,

while I like the fact that we have a deprecation strategy in general, I 
think we should weigh-in more factors when thinking about the final 
removal of methods instead of just following a strict rule of removal 
after two versions.

I think we should think more intensively of the pros and cons of the 
removal of a specific method in terms of:

* What are the benefits of the removal (e.g. does the removal make 
maintenance of the code drastically easier, or is it basically no 
problem to leave an old method in place)

* How frequently is a method used, e.g. in extensions. How many 
extensions will break.

As particular striking examples for very frequently used methods, I 
would name t3lib_div::intInRange() and t3lib_div::readLLXMLfile().

Of course we need to keep code maintainable. However, I think the fact 
that TYPO3's core code is at some points rather hard to maintain is 
mainly due to the very complex parts like TCEMain / TCEForms or the FE 
bootstrapping (which is now improving), and not so much because of 
t3lib_div containing a few more methods than would be desirable.

So, in short, I would be glad if we could consider the impact of such 
method removals and weigh it against the benefits.

cheers
Ingmar

Follow-up set to typo3.core.