Add more verbose warning for PHP 5.3.16

There was some confusion about the PHP 5.3.16 warning because 5.3.17 is not yet released.
Added a bit more info to clear things up.
Add reference to PHP bug #62874 for 5.3.16 requirement
Fixed an issue with installs from composer not working due to version conflict on symfony/symfony
merged branch jmather/patch-1 (PR #404)

Commits
-------

641ed4c Fixed an issue with installs from composer not working due to version conflict on symfony/symfony

Discussion
----------

Modified composer.lock to resolve install issue

Fixed an issue with installs from composer not working due to version conflict on symfony/symfony

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

by jmather at 2012-09-06T20:38:20Z

Again thanks to @tcstar for the help tracking the issue down and the refinement suggestions.
fixed composer file
merged branch kimausloos/master (PR #400)

Commits
-------

ece0516 Add reference to PHP bug #62874 for 5.3.16 requirement
dd09775 Add more verbose warning for PHP 5.3.16

Discussion
----------

Added a bit more info about the unreleased PHP 5.3.17 requirement when using PHP 5.3.16

There was some confusion about the PHP 5.3.16 warning because 5.3.17 is not yet released.
Added a bit more info to clear things up.

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

by bendavies at 2012-09-05T15:56:46Z

This doesn't really add anything.
I'd like to know the particular bug which prevents symfony working with 5.3.16...

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

by fabpot at 2012-09-05T16:02:03Z

@bendavies see https://bugs.php.net/bug.php?id=62874 But how does it help?

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

by bendavies at 2012-09-05T16:41:44Z

@fabpot there are already three recommendations that point to the actual php.
https://github.com/symfony/symfony-standard/blob/master/app/SymfonyRequirements.php#L516
https://github.com/symfony/symfony-standard/blob/master/app/SymfonyRequirements.php#L522
https://github.com/symfony/symfony-standard/blob/master/app/SymfonyRequirements.php#L528

So number 1, nice for consistency, and number 2, as an inquisitive person, i just like to know _why_.

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

by kimausloos at 2012-09-05T17:27:34Z

I think @bendavies is right, it improves consistency with other messages so I added the reference.
Revert "merged branch Tobion/patch-1 (PR #397)"

This reverts commit 85e19a5dda7b58e64b618f576d4014e3b1d9c55f, reversing
changes made to 22771ee4535b53bc2da4a67037619fd87201516f.
updated VENDORS for 2.1.1
added .travis.yml
Download Composer from a secure source
merged branch Maks3w/patch-1 (PR #417)

Commits
-------

ae36fb4 Download Composer from a secure source

Discussion
----------

Download Composer from a secure source
updated deps
reverted unwanted changes
finished reverting previous changes
merged branch bamarni/travis (PR #414)

Commits
-------

cf40c2b added .travis.yml

Discussion
----------

added .travis.yml

Added a travis.yml, mostly to check if the deps are solvable, and because this edition also has a unit test in it.

Could prevent issues like #406 #413

I didn't put the build status in the README not to pollute it.
updated VENDORS for 2.1.2
Update README.md

If you don't include the version of the Symfony's installation, you'll get an error if you try to install with composer.
merged branch joepicha/2.1 (PR #424)

Commits
-------

3114365 Update README.md

Discussion
----------

Update README.md

If you don't include the version of the Symfony's installation, you'll get an error if you try to install with composer.
Correcting YAML Markup in app/config to be valid YAML 1.2o

You cannot start a Plain Style Scalar with an Indicator (%). Play Style
Scalars which have a leading % should be changed to double-quote style
scalars.

fixes #426
You cannot start a Plain Style Scalar with an Indicator (%). Plain
Style Scalars which have a leading % should be changed to double-quote
style scalars.

for #426