[Process] Added ProcessUtils::escapeArgument() to fix the bug in escapeshellarg() function on Windows
[HttpKernel] made the classmap lazy-loaded
make twig extension handle custom template escaping guesser
[Validator] Added Polish translations for IBAN and ISBN messages.
[Validator] Added Slovak translations of IBAN and ISBN
[Validator] Russian translation of the IBAN & ISBN validator messages
[Validator] added Japanese translation for IBAN & ISBN messages
Fixed typo
typo fix
merged branch Olden/russian_translations (PR #7745)

This PR was merged into the master branch.

Discussion
----------

[Validator] Russian translation of the IBAN & ISBN validator messages

Added the Russian translation for new validators.

Commits
-------

ca00f21 [Validator] Russian translation of the IBAN & ISBN validator messages
merged branch patie/master (PR #7744)

This PR was merged into the master branch.

Discussion
----------

[Validator] Added Slovak translations for IBAN and ISBN messages.

Commits
-------

2890a3f [Validator] Added Slovak translations of IBAN and ISBN
merged branch jakzal/iban-isbn-pl-translations (PR #7743)

This PR was merged into the master branch.

Discussion
----------

[Validator] Added Polish translations for IBAN and ISBN messages.

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

Commits
-------

811fc30 [Validator] Added Polish translations for IBAN and ISBN messages.
merged branch 77web/translation-ja-iban-isbn (PR #7747)

This PR was merged into the master branch.

Discussion
----------

[Validator] added Japanese translation for IBAN & ISBN messages

| Q             | A
| ------------- | ---
| Fixed tickets | N/A
| License       | MIT

Commits
-------

3719cd5 [Validator] added Japanese translation for IBAN & ISBN messages
merged branch pborreli/patch-8 (PR #7748)

This PR was merged into the master branch.

Discussion
----------

Fixed typo

Commits
-------

173f15c Fixed typo
merged branch damour/patch-1 (PR #7749)

This PR was merged into the master branch.

Discussion
----------

changelog typo fix

Commits
-------

bc62d5b typo fix
Filesystem::touch() not working with different owners (utime/atime issue)
merged branch fabpot/moved_filesystem_3 (PR #7752)

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

Discussion
----------

Filesystem::touch() not working with different owners (utime/atime issue)

This PR was submitted on the symfony/Filesystem read-only repository and moved automatically to the main Symfony repository (closes symfony/Filesystem#3).

Case: I have 2 users, www-data and myself. I have a command script that makes a lock file in /var/lock/.../ something. This command is called from a post request by FOS and ran in the background.  Whever one of the 2 methods (web/cli manually) is used, the other user won't have permissions to use the Filesystem::touch(). The reason this won't work is the second parameter.

What touch() does:
$touch param: The touch time. If time is not supplied, the current system time is used.
$atime param: If present, the access time of the given filename is set to the value of atime. Otherwise, it is set to the value passed to the time parameter. If neither are present, the current system time is used.

So the current code is basically copying this. However, if the second parameter is null it is still present and will cause the same problem. Note that all files and folders related are set to 0777 and have the owner of www-data. I'm accessing them under my own account here:

Interactive shell

php > var_dump(touch('/var/lock/tripolis/ontw/dev/2140191804.lock', null));
PHP Warning:  touch(): Utime failed: Operation not permitted in php shell code on line 1

Warning: touch(): Utime failed: Operation not permitted in php shell code on line 1
bool(false)
php > var_dump(touch('/var/lock/tripolis/ontw/dev/2140191804.lock'));
bool(true)

If I were to pass it without second parameter, let it be time() or null (Filesystem uses time() by default if not present), it DOES work. However, Filesystem::touch() ALWAYS gives a parameter to touch. This parameter is exactly the same value as what the function itself would do in php. Let it be that in my case there is an issue with the atime. I'm not exactly sure how it works but it's not tracked or usable in my case. Because parameter 2 exists, parameter 3 is set. Parameter 3 is not allowed and therefore causes Filesystem::touch() to throw an exception.

Commits
-------

e3a0fe6 Filesystem::touch() not working with different owners (utime/atime issue)
[HttpFoundation] [HttpKernel] Internal sub-requests should have X-Forwarded-For header providing real client IP
merged branch guilhermeblanco/client_ip_fix (PR #7559)

This PR was squashed before being merged into the master branch (closes #7559).

Discussion
----------

[HttpFoundation] [HttpKernel] Internal sub-requests should have X-Forwarded-For header providing real client IP

This is a better alternative to fix issue highlighted in #7554 and #7557.

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #7554, #7557
| License       | MIT

When dealing with inline fragment renderer, it emulates an internal request by overriding the REMOTE_ADDR on Request. This is true, since conceptually request came from local server.
The problem that this introduces is that overriding the server value, it turns into an impossible state to retrieve the real client ip, only returning the local server IP (which is hardcoded to 127.0.0.1).

This patch takes the same approach as a Varnish call (it behaves the exact same way, reusing all code built for handling client ip handling on sub-requests), populating the X-Forwarded-For header and also making getClientIp smarter by removing possible local IP addresses from being considered as the client IP address.

Commits
-------

773e109 [HttpFoundation] [HttpKernel] Internal sub-requests should have X-Forwarded-For header providing real client IP
[HttpKernel] optimized previous merge