[Validator] Renamed deprecated Size constraint to Range
[Validator] Removed MinCount and MaxCount and replaced them by the constraint Count
[Validator] Deprecated the constraints Min and Max in favor of Range
[Validator] Added Length constraint and deprecated MinLength and MaxLength
bumped Symfony version to 2.0.17-DEV
fixed swiftmailer requirement in composer file
merged branch brikou/fix_composer (PR #4867)

Commits
-------

f748885 fixed swiftmailer requirement in composer file

Discussion
----------

Fix composer
[Form] Improved ChoiceType performance by caching ChoiceList objects
fix another '0' problem
merged branch bschussek/range_count_length (PR #4863)

Commits
-------

a92f80b [Validator] Added Length constraint and deprecated MinLength and MaxLength
83a3f75 [Validator] Deprecated the constraints Min and Max in favor of Range
0cdacee [Validator] Removed MinCount and MaxCount and replaced them by the constraint Count
741c147 [Validator] Renamed deprecated Size constraint to Range

Discussion
----------

[Validator] Reintroduced Range constraint and created Count and Length constraints

Bug fix: no
Feature addition: no
Backwards compatibility break: no
Symfony2 tests pass: yes
Fixes the following tickets: -
Todo: -

After @Tobion's comment to #4851, this is the next try to streamline the constraints and reduce duplication of logic. The downside of the current MinLength/MaxLength and MinCount/MaxCount pairs is that they cannot output a fitting error message if a value should have an *exact* length/count. So this PR introduces

* Range (formerly Size) to replace Min/Max
* Count to replace MinCount/MaxCount
* Length to replace MinLength/MaxLength

Feedback is appreciated.

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

by Tobion at 2012-07-11T20:40:08Z

The `choice` constraint also cannot handle `min = max`. Or maybe we don't need these options on choice anymore as we can achieve the same with the new `count` constraint?!

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

by beberlei at 2012-07-12T08:59:44Z

Dude, nobody has time to fix the BC breaks you introduce :-)

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

by TomAdam at 2012-07-12T12:38:49Z

The changes to the `Size` validator yesterday broke my project, and I started rewriting to use `MaxLength / MinLength` validators today, until I spotted this. It would be good if this PR could have a reasonably high priority (whether or not it is accepted) as it will change how I fix my issues. I suspect a lot of people using the master branch will be in the same situation.
merged branch Tobion/patch-2 (PR #4878)

Commits
-------

d83d65a fix another '0' problem

Discussion
----------

fix another '0' problem
[Form] Improved EntityType performance by caching the EntityChoiceList
[OptionsResolver] Made the OptionsResolver clonable
merged branch bschussek/performance (PR #4881)

Commits
-------

a924dab [OptionsResolver] Made the OptionsResolver clonable
70307e5 [Form] Improved EntityType performance by caching the EntityChoiceList
8298d8c [Form] Improved ChoiceType performance by caching ChoiceList objects

Discussion
----------

[Form] Improved performance of ChoiceType and EntityType

Bug fix: no
Feature addition: no
Backwards compatibility break: no
Symfony2 tests pass: yes
Fixes the following tickets: -
Todo: -
[Form] Removed invalid PHPDoc text
[HttpKernel] removed obsolete code (the status code is already taken care of in FlattenExceptiondirectly)
[HttpKernel] moved some mis-placed logic to FlattenException
[Routing] fixed ApacheUrlMatcher and ApachMatcherDumper classes that did not take care of default parameters in urls.
[Console] Added LG char escaping test.
[Console] Fixed output formatter regex.