[HttpKernel] added a way to enable a disable Profiler
[FrameworkBundle] added a way to enable the profiler for the very next request in functional tests (closes #4307)
[FrameworkBundle] recursively resolve container parameter placeholders
for arrays in router _defaults
Added CardScheme validator
Add Luhn validator
handle inheritance in config:dump-reference when a bundle name is passed to the command
OptionsResolver#validateOptionTypes should check if option value exists before checking its type; added corresponding test

OptionsResolver#validateOptionsCompleteness would already have thrown exception if the option were required, so this should only affect something explicitly marked as optional
validateOptionTypes checking existence of key rather than value
StreamedResponse always sends a HTTP 1.1 response

SERVER_PROTOCOL is "Name and revision of the information protocol via which the page was requested; i.e. 'HTTP/1.0'"
[Validator] Updated Spanish translations
merged branch chx/master (PR #5175)

Commits
-------

b00ea41 StreamedResponse always sends a HTTP 1.1 response

Discussion
----------

StreamedResponse always sends a HTTP 1.1 response

SERVER_PROTOCOL is "Name and revision of the information protocol via which the page was requested; i.e. 'HTTP/1.0'". The condition was for 1.0 which is wrong.

Earlier I filed #5173

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

by travisbot at 2012-08-03T18:33:45Z

This pull request [fails](http://travis-ci.org/symfony/symfony/builds/2030496) (merged b00ea417 into be41ca35).

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

by chx at 2012-08-03T18:36:58Z

Seems to me that the Travis fails have absolutely nothing to do with my patch.
[HttpFoundation] fixed typo (refs #5175)
[HttpFoundation] fixed tests (refs #5175)
merged branch franmomu/patch-2 (PR #5177)

Commits
-------

981da1a [Validator] Updated Spanish translations

Discussion
----------

[Validator] Updated Spanish translations

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

by travisbot at 2012-08-03T23:06:26Z

This pull request [passes](http://travis-ci.org/symfony/symfony/builds/2032706) (merged 981da1a9 into be41ca35).
merged branch EvanK/master (PR #5132)

Commits
-------

aa890ae validateOptionTypes checking existence of key rather than value
c6a9638 OptionsResolver#validateOptionTypes should check if option value exists before checking its type; added corresponding test

Discussion
----------

[OptionsResolver] validateOptionTypes raises error for optional, nonexistant option values

The [`OptionsResolver#validateOptionTypes`](https://github.com/symfony/OptionsResolver/blob/master/OptionsResolver.php#L315) method should check if a given option value exists before trying to test its type:

```php
<?php
// Two optional 'one' and 'two' options that, if they exist, must be a string and int respectively
$resolver = new OptionsResolver();
$resolver->setOptional(array('one', 'two'))->setAllowedTypes(array('one' => 'string', 'two' => 'int'));

// Correctly fails as wrong type
$resolver->resolve(array('one' => 1, 'two' => 'alpha'));

// Correctly succeeds
$resolver->resolve(array('one' => 'alpha', 'two' => 1));

// Raises error "Undefined index: two", see OptionsResolver.php line 315
$resolver->resolve(array('one' => 'alpha'));
```

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

by travisbot at 2012-08-01T01:46:50Z

This pull request [passes](http://travis-ci.org/symfony/symfony/builds/2006049) (merged c6a9638a into b1618d21).

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

by ericclemmons at 2012-08-03T05:15:27Z

I hope this makes it in for the 2.1 release.  We have several types attempting to take advantage of the `OptionsResolver` component and want to help resolve this.

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

by stof at 2012-08-03T07:30:44Z

:+1:

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

by travisbot at 2012-08-03T17:25:12Z

This pull request [passes](http://travis-ci.org/symfony/symfony/builds/2030053) (merged aa890aed into b1618d21).
updated VERSION for 2.1.0-RC1
bumped Symfony version to 2.1.0-DEV
fixed merge
[Routing] fixed 4 bugs in the UrlGenerator
Added Yaml\Dumper::setIndentation() method to allow a custom indentation level of nested nodes.

YAML does not specify an absolute indentation level, but a consistent indentation of nested nodes only: http://www.yaml.org/spec/1.2/spec.html#space/indentation/

Projects that are generally using 2 spaces for indentation should be able to retain consistency with their coding standards by supplying a custom value for the new $indent parameter added to Yaml::dump(), or the new Dumper::setIndentation() method.

The new parameter is a backwards-compatible API addition and defaults to the previous default of 4 (which was changed from 2 via PR #2242 only recently).