Symfony 2.0.10 has just been released:
Twig has been updated to 1.6.0 (which fixes a bug when using Assetic in the production environment);
Doctrine has been updated to their latest minor versions;
And as always, some minor bugs has been fixed.
The CHANGELOG has all the details about the changes done in this release and you can also have a look at the full diff.
If you are starting a new project, you can get the Symfony Standard Edition distribution on the download page.
If you already have a project based on the Symfony Standard Edition 2.0.x, you can easily upgrade to 2.0.10 by getting the new deps and deps.lock files.
Then, run the vendors script (it also clears your cache):
$ ./bin/vendors install
Remember that the Symfony2 Components are also available as standalone
libraries. You can get them via their dedicated read-only repositories on
Github (https://github.com/symfony/Finder
for instance), install them via
PEAR (pear install symfony2/Finder
), or even
install them via Composer.
Excelente!!!
For 2.0.9 projects, other than getting the new deps and deps.lock files, this time you also need to update the bin/vendors script since there's been some changes.
https://github.com/symfony/symfony-standard/commit/36ad2123ecab34e68216efc94680eecdca4197cf
Carlos Zuniga, thanks for the tip. I'll test it later.
Excellent.
Nice to see this in the changelog:
Make DoctrineBundle fowards compatible with Doctrine 2.2
Go!
Twig 1.6, excellent!
Hi everyone,
I have an error when i want to update SF2 from 2.0.9 to 2.0.10.
""swiftmailer" has local modifications. Please revert or commit/push them before running this command again."
Could you help me ?
Thanks!
All right, it works with this command :
$ ./bin/vendors install --reinstall
greetings symfony developers.
at first, i have to say that you are doing great job, symfony2 found a place in my heart since it's first RC versions.
but please, can you tell us release date for 2.1, even roughly approximate?
i am about starting a project, and i need to decide between buliding it on 2.0.x and then upgrade to 2.1, or just wait for 2.1.
i've noticed there are many BC breaks in 2.1 , so the second option would be better imho, but it also depends on when the 2.1 version will be released.
i've found a post by Fabien Potencier in GG, in which he was talking about December '11. not out yet, so i believe it is about to come out soon.
do you plan to release within a month? or longer?
perhaps you can't tell the exact date, but if you can tell approximately (the month), it will be enough info for me (and i suppose not only for me) to decide whether to wait or not.
thank you in advance. korek.
why there is an error with the .gz and .zip archives when trying to download and extract???
and errors when using new deps and deps.lock files for upgrading from 2.0.9 to 2.0.10 ??? thx
Thank you for this release.
Don't forget to recompile the Twig extension for those using it, or it will result in execution exceptions under certain circumstances!
Hi,
I don't know where to contact symfony to let you know that I can't download the file: http://symfony.com/download?v=Symfony_Standard_Vendors_2.0.10.tgz or zip version.
I have tried to download several times with the same result "the file is corrupted", because the size of the file downloaded is at best 1.8 MB against the original file 2.9 MB. As I said, I have tried to download since 2.0.9 release with the same results, and of course I can download *.tgz, .zip, rar from internet with no problems like this.
Thank you.
Please update the deps.lock for doctrine-common to be 2.1.6 not 2.1.4 it breaks the upgrade process, thanks!
If you are using doctrine-mongo-db bundle you must set up the version tag to this commit "6b0c0bf29409b69902cdd23eb7e9a0138759daac", so doctrine-mongo-db bundle keeps compatible with the ORM layer.
S2.10 is Excelente
but i need to know if there a way to delete generated cruds the way like we create it ??? ex.. we use ./app/console doctrine:generate:crud to create cruds so what about a way to drop cruds ??
After updating to 2.0.10 I noticed there is variable $parameters present inside view. I have noticed that because I was passing such variable from controller into view and after update I faced conflict. Can anyone point me that change in changelog please?
As always, thank you Fabien for the wonderful work!
Great!