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

[Ingo Renner]

Hi all,

This is an SVN patch request.

Type: Bugfix / New feature

Bugtracker references:
http://bugs.typo3.org/view.php?id=14729

Branches:
trunk

Problem:
The deprecation log has been disabled by default with issue #14339 and 
committed in r7616.
However, by disabling the deprecation log by default there's no chance 
for regular users to know when extensions are using deprecated APIs. 
When these APIs are going to be removed eventually with a later release, 
these users may experience crashes and fatal errors which could have 
been avoided if they had seen the deprecation log messages. This is bad 
in regards of user experience.

The deprecation log was created to allow for cleaning up and eventually 
removing old APIs and to still stick with backwards compatibility by 
letting users and developers know when they are using APIs that are 
subject to removal. Thus when not indicating use of these APIs to users 
and developers, disabling the deprecation log is like throwing over 
board our responsibility for backwards compatibility we have been so 
proud of the last years.



Solution:
The attached patch re-enables the deprecation log by default and 
introduces a new status report as described below.

It is true that the deprecation log can grow to quite some size. 
Therefor a new status report entry will be added by the attached patch 
to let the user know whether the deprecation log is enabled, whether 
certain file sizes are reached, and what the current log file's size is.

Depending on the size of the log file the status will be OK for disabled 
deprecation log, NOTICE for enabled deprecation log, WARNING for 10MB+, 
and ERROR for 100MB+



all the best
Ingo


-- 
Ingo Renner
TYPO3 Core Developer, Release Manager TYPO3 4.2

-------------- next part --------------
A non-text attachment was scrubbed...
Name: enable_deprecation_log.diff
Type: text/x-diff
Size: 9377 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20100615/ff50d812/attachment.diff>