TYPO3 Core

Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/59566

Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/59566

Patch set 8 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/59566

Patch set 9 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/59566

Patch set 10 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/59566

Just a small note:
If the configurePlugin call still uses the old controller name without the fully qualified class name and a class with that name exist, the automatic fallback does not work:
ExtensionUtility.php#L76

I don't think there are many instances were this is a problem, but I had a SmartyController and the class Smarty exists, so this code did not work in TYPO3 v10:

\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
    'VierwdSmarty',
    'smarty_render',
    ['Smarty' => 'render',],
    []
);

I got this exception:

#1476109646 TYPO3\CMS\Extbase\Mvc\Exception\InvalidControllerException
Invalid controller "Smarty". The controller must implement the TYPO3\CMS\Extbase\Mvc\Controller\ControllerInterface.

As I said: I do not think there are many (or even any ;-)) extensions, were this is a problem. I just wanted to leave this note, if someone else has this problem.