Updated the demo application to Symfony 2.7

[javiereguiluz]

This fixes #71

[xabbuh]

You should also commit the changes to the composer.json file.

[javiereguiluz]

@xabbuh I did ... there is none :)

[xabbuh]

But there should be a difference if you bump the requirement to Symfony 2.7.

[javiereguiluz]

@xabbuh in the .lock file yes, but not in the .json file (we use ~2.6 for Symfony)

[javiereguiluz]

By the way, I updated Symfony following the recommendation of @weaverryan:

$ composer update symfony/symfony sensio/distribution-bundle --with-dependencies

[xabbuh]

To be more clear: You now make use of the configureOptions() method which introduced in Symfony 2.7. So having a version constraint like that if wing as you cannot use the form types with Symfony 2.6.

[javiereguiluz]

OK. I understand you now :) Should I use 2.7.* or ~2.7?

[xabbuh]

Not sure if that really matters. What was the reasoning for the old constraint?

[javiereguiluz]

There was no particular reasoning. I always use the ~ constraint, so let's keep using ~2.7. Thanks.

[stof]

@javiereguiluz what about updating other deps too (DoctrineBundle got a new release for instance)

[javiereguiluz]

@stof I fully agree! The constraint is now ~1.5 and I've executed composer update doctrine/doctrine-bundle --with-dependencies

The current constraints are as follows. Should we update any other dependency?

    "require": {
        "php"                                  : ">=5.3.3",
        "ext-pdo_sqlite"                       : "*",
        "doctrine/doctrine-bundle"             : "~1.5",
        "doctrine/doctrine-fixtures-bundle"    : "~2.2",
        "doctrine/orm"                         : "~2.2,>=2.2.3",
        "erusev/parsedown"                     : "~1.5",
        "incenteev/composer-parameter-handler" : "~2.0",
        "ircmaxell/password-compat"            : "~1.0",
        "leafo/scssphp"                        : "~0.1.",
        "patchwork/jsqueeze"                   : "~1.0",
        "sensio/distribution-bundle"           : "~3.0.12",
        "sensio/framework-extra-bundle"        : "~3.0",
        "symfony/assetic-bundle"               : "~2.3",
        "symfony/monolog-bundle"               : "~2.4",
        "symfony/swiftmailer-bundle"           : "~2.3",
        "symfony/symfony"                      : "~2.7",
        "twig/extensions"                      : "~1.0"
    },

[stof]

Well, you should probably update all deps to their latest stable versions (incenteev/composer-parameter-handler has a new release too to avoid deprecation warnings on Symfony 2.7 for instance)

[javiereguiluz]

OK then. I've updated everything to their latest versions.

[weaverryan]

btw, we used the 2.6.* format in composer.json for symfony/symfony just to match the SE. But I don't think it's a problem to differ from it - as long as we're doing something "good" :).

[weaverryan]

👍

[weaverryan]

@javiereguiluz for the future - I had an idea. We could upgrade a branch of the symfony-demo during the stabilization phase of a Symfony version. Then, it'll be ready for the release. But more importantly, it might help identify any bugs or not-smooth upgrade paths, while those can still be fixed :).

[javiereguiluz]

@weaverryan I like the idea and I'm going to implement it for 2.8. Thanks!