merged branch schmittjoh/patch-1 (PR #199)
merged branch schmittjoh/patch-1 (PR #199)

Commits
-------

a65eec7 use the BC branch

Discussion
----------

use the BC branch

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

by fabriceb at 2011/09/14 02:01:37 -0700

The most dangerous BC breaks are those which change the configuration settings (which Johannes just did in JMSSecurityExtraBundle). Because you might update all the dependencies to their correct versions, and still have a major break in your application because of a configuration parameter not in the new format.

I am therefore strongly in favor of fixing all revisions of all bundles in the Symfony standard edition.

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

by stof at 2011/09/14 05:11:12 -0700

@fabriceb The SE comes with locked version in deps.lock which should be used.

@schmittjoh you need to check the version in deps.lock

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

by mbadolato at 2011/09/14 09:26:49 -0700

The SE (at least the github download) has deps.lock updates to it that break the distribution. There were changes yesterday (to a few dependancies) and Twig broke, for instance. Also, until yesterdays updates, it was locked at 2.0.0 and not the current 2.0.1 release.

Should the github repository no longer be used for SE downloads, making the packaged download the only real distribution? That's fine if it is, I'm just curious because I track the Git repository and still do merge updates to my project when I see them, to ensure I'm staying current with SE. So, if I need to stop doing that and just wait for packaged release, I can do that.  My question to packaged releases, though, is when update s are done, can we rely on just updating deps and deps.lock, or will we also need to update things in app/ and bin/ etc?

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

by stof at 2011/09/14 09:43:50 -0700

@mbadolato Use the 2.0 branch of the symfony-standard repo if you want to use the BC version, or keep the released version.
For 2.0.x releases, the deps and deps.lock should be enough. For 2.1, you will maybe need some changes in the config but this will be documented when it will be released.

mbence/csaladsegito,mbence/csaladsegito,mbence/csaladsegito