[TYPO3-core] RFC #14729: Backwards compatibility brocken by disabled deprecation log

[Patrick Gaumond]

On 2010-06-15 14:54, Ingo Renner wrote:

> I see it like this: You and all the admins out there are responsible for
> turning off deprecation log in production environments. We as the core
> team are responsible to not let people run into unexpected crashes we
> can avoid.

Having an invisible log doesn't bring anything. Until 4.5 and a future 
patch, I consider the way the log is acting as buggy. Really.

Bug #1: It's hidden
Bug #2: There's no size limit to it.

One solution against monster logs (and that's what I'm trying to avoid) 
would be to have the log limit itself in size. Let's say 1 MB max.

Then I would call Bug #1 a UX bug.

The current situation could generate a 5 GB file in few weeks for people 
unaware of the existence of the log...

> A lot of enterprises still value backwards compatibility more than
> performance as hardware is cheap and performance can be increased by
> many means.

The log *itself* doesn't bring or increase compatibility.

> Also, are you the one going to answer people's questions once 4.6 is out
> in a year from now? Why there installation is not working anymore? Are
> you going to keeping the bugtracker clean then when their installations
> crash because they have extensions installed that use deprecated APIs
> which they didn't notice? Also by disabling the deprecation log
> developers who are new to TYPO3 may step into the same trap and blame it
> on us core developers. What if TYPO3 gains a reputation of being crashy,
> people stopping using it and some people loosing their jobs. I wouldn't
> be very happy with that.

http://en.wikipedia.org/wiki/Apocalypse

;-)

> Either way I (and probably the core team, too) don't wanna be blamed for
> breaking installations and as mentioned before admins are responsible to
> turn the log off when going live.

Again, the deprecation log doesn't fix anything.

Ingo, I will not run at you throwing rocks. I respect the job you did 
for TYPO3 as a whole. I just disagree for this single feature. I will 
not comment anymore on this precise subject. If the logs gets back by 
default I will work with it and survive.

Patrick