TYPO3 Core

Patch set 1 of change Ie54e6b0f1d22035b17dad59ec8fea7b1b2f644f1 has been pushed to the review server.
It is available at http://review.typo3.org/5693

Patch set 1 of change I996203d09e9557cfb301d079bbb026a32626c0d5 has been pushed to the review server.
It is available at http://review.typo3.org/5696

Patch set 1 of change I79bad0449509675e3660081ed727799e0ad0353b has been pushed to the review server.
It is available at http://review.typo3.org/5697

Patch set 2 of change Ie54e6b0f1d22035b17dad59ec8fea7b1b2f644f1 has been pushed to the review server.
It is available at http://review.typo3.org/5693

Patch set 3 of change Ie54e6b0f1d22035b17dad59ec8fea7b1b2f644f1 has been pushed to the review server.
It is available at http://review.typo3.org/5693

Patch set 1 of change Ie690faa39a11ca866464fa2c294cfc980d763bb7 has been pushed to the review server.
It is available at http://review.typo3.org/5709

The debug call was used to force the users to change their Ext.Direct extensions by opening annoying information windows, because of the criticality of the security hole. IMHO it's ok to change that to the deprecationLog method as this is always visible instead of the pure debug call.