[TYPO3-dev] Getting rid of deprecated TypoScript stuff in TYPO3

[Oliver Hader]

Hi Jürgen,

Juergen Egeling schrieb:
> HI,
> * Oliver Hader <oliver at typo3.org> [081104 17:18]:
>> Several months/years ago we agreed on marking code in the TYPO3 Core
>> with the PHPDoc tag "@deprecated" and will remove the class or method
>> two minor releases later. This means a functionality marked as
>> deprecated in TYPO3 4.1 will be removed in TYPO3 4.3.
> 
> You really _have_ to notify each TYPO3 admin each and individually
> by guiding him/her.
> If you remove deprecated features, it will be a nightmare for _all_
> hosters that in this case cannot automatically update TYPO3 websites.
> From that point on they would not be able to updates TYPO3, even
> if there is a severe bug in the next version.
> IMHO with the next release there has to be a tool, that the installer
> runs that tells the admin, that in release N+1 the following features
> won't work, IMHO also it has to show the specific problems that this
> admin than is awaiting.
> 
>> Personally I'm in for "c)" but wanted to know about your opinion on that.
> 
> Who of you is in charge of TYPO3.org and checked  if this will still work?

Thanks for your meaty input! That's exactly the reason why this
discussion/question was put to the public instead of just removing
things with a FYI-message in the core list. I know that there will be
problems on specific systems using elderly extensions that refer to
functionalities that got deprecated in between.

To capture calls to deprecated stuff or the usage of deprecated
functions there can be an "overlay" that puts a warning into a logfile.
This overlay can be disabled if a website is in an productive environment.

olly
-- 
Oliver Hader
TYPO3 Release Manager 4.3