[TYPO3-core] Strategy for deprecation log
Jost.Baron at gmx.de
Wed Apr 3 15:03:47 CEST 2013
Am 4/3/2013 2:45 PM, schrieb Markus Klein:
>> I also think that dev mode is not a good idea. If someone needs such a mode,
>> he can create a TS constant to switch it on and off. That way, other
>> functionality (switch CSS/JS compression on or off, etc.) could easily be done
> Typoscript is not even nearly in the scope of this feature. Deprecation is happening at a very very low level of code and might appear where TS is not even close to be loaded.
> Furthermore TS is always page specific, whereas deprecation is for the whole installation, independent of actual pages.
Thats a point. But then, the current mode should at least be checkable
in TS, so one change configuration depending on the mode.
> Deprecation is not for integrators!! Integrators can change nothing, but posting a ticket at forge for the respective extension.
Only the exact details are not. It is vital for an integrator to be
warned that something could go wrong in the (near) future and might need
attention. It is his choice what he does with the warning - he might
investigate (if he is a dev as well), open a ticket, ignore the message
or switch these messages off. But these things need to be done
consciously, so he is aware that there could be problem in the future.
More information about the TYPO3-team-core