merged branch pborreli/console-progress-precision (PR #5735)

This PR was merged into the master branch.

Commits
-------

61be89d [Console] [ProgressHelper] better percentage precision

Discussion
----------

[Console] [ProgressHelper] better percentage precision

With this code :
```php
$progress = new ProgressHelper();
$progress->start($output, 50);
$progress->display();
$progress->advance();
$progress->advance();
$progress->advance();
$progress->advance();
$progress->advance();
$progress->advance();
```
The output was :
```
  0/50 [>---------------------------]   0% // float(0)
  1/50 [>---------------------------]   0% // float(0)
  2/50 [>---------------------------]   0% // float(0)
  3/50 [==>-------------------------]  10% // float(0.1)
  4/50 [==>-------------------------]  10% // float(0.1)
  5/50 [==>-------------------------]  10% // float(0.1)
  6/50 [==>-------------------------]  10% // float(0.1)
```
With this PR :
```
  0/50 [>---------------------------]   0% // float(0)
  1/50 [>---------------------------]   2% // float(0.02)
  2/50 [=>--------------------------]   4% // float(0.04)
  3/50 [=>--------------------------]   6% // float(0.06)
  4/50 [==>-------------------------]   8% // float(0.08)
  5/50 [==>-------------------------]  10% // float(0.1)
  6/50 [===>------------------------]  12% // float(0.12)
```
Tests are included.

---------------------------------------------------------------------------

by sstok at 2012-10-13T09:22:22Z

:+1:
Fix incorrect variable in FileProfilerStorage
merged branch merk/patch-4 (PR #5738)

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

Commits
-------

894377f Fix incorrect variable in FileProfilerStorage

Discussion
----------

[HttpKernel] [Profiler] Fix incorrect variable use in FileProfilerStorage

Bug fix: yes
Feature addition: no
Backwards compatibility break: no
Symfony2 tests pass: yes
Fixes the following tickets: ~
Todo: ~
License of the code: MIT
Documentation PR: ~

---------------------------------------------------------------------------

by pborreli at 2012-10-13T06:58:57Z

:+1:

---------------------------------------------------------------------------

by sstok at 2012-10-13T09:20:33Z

This should be done 2.1 as the bug also existing there.
[WebProfilerBundle] fixed typos
[HttpKernel] unified the way the traceable event dispatcher injects information into the profiler (closes #5733)
[WebProfilerBundle] removed dependency on the templating component
[WebProfileBundle] remove dependency on the DIC

The controllers are not relying on the DIC anymore and only Twig
is used for rendering (instead of the Templating component).

The Exception controller has not been updated yet as it relies on many
external dependencies (and other bundles).
[WebProfilerBundle] fixed typo
[TwigBundle] Moved the registration of the app global to the environment

This makes the app global variable available also when accessing the Twig
environment directly instead of using the TwigEngine.
[WebProfilerBundle] Remove the now unneeded BC var and fixed a typo
[Validator] fixed German translation, see #5675
merged branch craue/patch-24 (PR #5743)

This PR was merged into the master branch.

Commits
-------

d427522 [Validator] fixed German translation, see #5675

Discussion
----------

[Validator] fixed German translation

see #5675
[WebProfilerBundle] fixed tests
[HttpKernel] removed test that is not needed anymore
moved the traceable controller resolver from the framework bundle to the HttpKernel component (using composition now)
[WebProfilerBundle] fixed some tests
Fix a few namespaces to match file system.
Made the router lazy when setting the context

Initializing the matcher and the generator to set the context does not make
sense as it is set anyway when building them. This avoids initializing
them in the RouterListener if you never actually use them (for instance
because you use the apache matcher).
merged branch stof/lazy_router (PR #5745)

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

Commits
-------

a6918ec Made the router lazy when setting the context

Discussion
----------

Made the router lazy when setting the context

Initializing the matcher and the generator to set the context does not make
sense as it is set anyway when building them. This avoids initializing
them in the RouterListener if you never actually use them (for instance
because you use the apache matcher).

@fabpot should it be considered as a bugfix (and so done in older branches) or a new feature ?

---------------------------------------------------------------------------

by stof at 2012-10-14T01:23:51Z

Btw, looking at the ApacheUrlMatcher code, I think it is flawed and that this change will actually not fix the performance issue reported in #5538 as it requires creating the RouteCollection everytime, including when apache actually matched it.
merged branch dpb587/pr-cleanup-some-tests (PR #5737)

This PR was merged into the master branch.

Commits
-------

3d2a7db Fix a few namespaces to match file system.

Discussion
----------

Cleanup Some Tests - tearDown and namespaces

Tried to cleanup a few tests and fix a few test classes which weren't following PSR-0. Removed original `tearDown` changes.

---

Bug fix: no
Feature addition: no
Backwards compatibility break: no
Symfony2 tests pass: yes
Fixes the following tickets: ~
Todo: ~
License of the code: MIT
Documentation PR: ~

---------------------------------------------------------------------------

by pborreli at 2012-10-13T06:41:14Z

from [PHPUnit documentation](http://www.phpunit.de/manual/current/en/fixtures.html#fixtures.more-setup-than-teardown) :

>setUp() and tearDown() are nicely symmetrical in theory but not in practice. In practice, you only need to implement tearDown() if you have allocated external resources like files or sockets in setUp(). If your setUp() just creates plain PHP objects, you can generally ignore tearDown(). However, if you create many objects in your setUp(), you might want to unset() the variables pointing to those objects in your tearDown() so they can be garbage collected. The garbage collection of test case objects is not predictable.

---------------------------------------------------------------------------

by fabpot at 2012-10-13T10:05:49Z

All these tearDown methods are not needed and should be removed.