Moved services config into a dedicated file.
(cherry picked from commit 581de28)
Added a central service to provide directory names etc. This should be used to handle what is currently done by the DatabaseUpdateProvider interface.
(cherry picked from commit 1220bd0)
Added export, i. e., reverse mapping from object properties to column names. The reverse operation of hydrate.
(cherry picked from commit e480229)
Completed mapping of config items to provide functionality required during INSERT and UPDATE operations.
(cherry picked from commit 5619aba)
generalized existing selectOrInsert to "merge", i. e. a method that will run updates as well, if the record already is in the db. In doing so, refactored the existing code such that the unsafe (i. e., not transaction-wrapped) methods have protected access again (this had not been possible before due to the way a closure was used).
(cherry picked from commit 87260d6)
Building upon recent changes to the mapper and db service, implemented a method to write back configuration options into the db.
(cherry picked from commit 12e0c7e)
Overriding templates for FOSUserBundle.
(cherry picked from commit 893feb8)
Fixed mailer setup.
(cherry picked from commit 0da9eec)
Added a "root" user that is defined in the config files and that can be used to bootstrap the user setup during installation.
(cherry picked from commit c9106fb)
Added a translatable exception and, derived from that, a specific exception to be raised in defensive code blocks, this could be used later to create bug reports automatically etc.
(cherry picked from commit 8aea9fc)
Changed the menu handling to an extender pattern, where controllers can register their menu entries at the menu manager, and a dedicated controller can be used to render the menu in a template. This allows bundles to influence the menu without the rendering controller needing to know about it.

Currently, there's a method on the menu extending controllers that returns a hardcoded array structure which is used to construct the menu tree. This should be changed to a mechanism driven by configuration files.
(cherry picked from commit 89d5140)
Fixed enabling of config file defined "root" user by properly setting up chained providers.
(cherry picked from commit 1504a4a)
Implemented role-dependent menu entries. Child nodes currently can not have less strict access requirements than their parents. This could be changed to either removing the targets from disallowed parents, and / or continuing to process the children if the parent does not have a target, even if the parent is not allowed.

Currently, all menu items get a default access level of ROLE_USER (i. e., the actual access level is still a dummy, even though the processing works correctly).
(cherry picked from commit 9c0dec1)