[Form] Choice children can be template customized like collection
[Serializer] Added PropertyNormalizer, a new normalizer that maps an object's properties to an array
Call AuthenticationManager in AnonymousAuthenticationListener
[HttpKernel] Extract method to make callable controller in ControllerResolver

correct naming
add allow_html5 option to date and time FormType to disable HTML5 date input when widget is set to single_text

remove unnecessary test when creating datetime format data transformer
[WebProfilerBundle] turbolinks compatibility
[OptionsResolver] Added a light-weight, low-level API for basic option resolving
[HttpFoundation] Silent only JSON errors
Catch exceptions to restore the error handler
Fix JsonSerializable namespace
Clear json_last_error
bug #11418 [JsonResponse] Silent only JSON errors (GromNaN)

This PR was submitted for the master branch but it was merged into the 2.5 branch instead (closes #11418).

Discussion
----------

[JsonResponse] Silent only JSON errors

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | maybe
| Fixed tickets | #11415
| License       | MIT
| Doc PR        | n/a

Commits
-------

6d6a3af Clear json_last_error
ef91f71 Fix JsonSerializable namespace
d952f90 Catch exceptions to restore the error handler
ddf95c7 [HttpFoundation] Silent only JSON errors
check for the Validator if forms are enabled

When the Form component is enabled, the container extension class
automatically enables the Validator component which therefore has to
be enabled. The container extension now throws an exception when forms
are enabled, but the Validator component is not present.
bug #11839 [FrameworkBundle] check if the Validator component is present when forms are enabled (xabbuh)

This PR was merged into the 2.5 branch.

Discussion
----------

[FrameworkBundle] check if the Validator component is present when forms are enabled

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets |
| License       | MIT
| Doc PR        |

The `Symfony\Component\Validator\Validation` class is used in the
`FrameworkExtension` class. Therefore, it is required to have the
Validator component installed in production as well but not only when
being in a development environment.

Commits
-------

ed41da1 check for the Validator if forms are enabled
[Translation] [Config] Clear libxml errors after parsing XML file
Avoid question mark and asterisk in folder names to prevent windows filesystem issues.

A previous commit introduced a folder with a question mark and an asterisk which are invalid NTFS folder name characters and prevented checkout on those systems.
bug #11908 [Translation] [Config] Clear libxml errors after parsing xliff file (pulzarraider)

This PR was merged into the 2.3 branch.

Discussion
----------

[Translation] [Config] Clear libxml errors after parsing xliff file

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | -
| License       | MIT
| Doc PR        | -

If libxml_use_internal_errors is set to `true` before parsing xliff file, the libxml errors are not cleared correctly. An error `Validation failed: no DTD found !` occurs in libxml errors after parsing and it's available outside the xliff parser (can break other functionality that use `libxml_get_errors` function).

Commits
-------

fab61ef [Translation] [Config] Clear libxml errors after parsing XML file
typo fixed in AbstractProcessTest (getoutput() => getOutput())
minor #11986 typo fixed in AbstractProcessTest (getoutput() => getOutput()) (YevKov)

This PR was submitted for the master branch but it was merged into the 2.3 branch instead (closes #11986).

Discussion
----------

typo fixed in AbstractProcessTest (getoutput() => getOutput())

Commits
-------

36998bb typo fixed in AbstractProcessTest (getoutput() => getOutput())
bug #11989 [Finder][Urgent] Remove asterisk and question mark from folder name in test to prevent windows file system issues. (Adam)

This PR was merged into the 2.3 branch.

Discussion
----------

[Finder][Urgent] Remove asterisk and question mark from folder name in test to prevent windows file system issues.

Bugfix: Yes
Fixed tickets: #11984 , #11985
Related tickets: #11970

Commit #11970 prevented Symphony from being checked out via windows due to invalid characters in a folder name within the tests.

The issue was reported in #11984  and was attempted to be fixed in #11985 but wasn't due to still including the question mark.

Please accept this ASAP as it entirely breaks any composer that relies on it.

Commits
-------

5fbb278 Avoid question mark and asterisk in folder names to prevent windows filesystem issues.