📜 ⬆️ ⬇️

Symfony 2.2 - Already Here!

image
It is finished! Symfony 2.2 is now available for download and this is the first release of Symfony2 which was produced in accordance with our new release process . First of all, I would like to heartily thank the Symfony team (developers, authors, bloggers) who helped us with this release. Everyone has done a tremendous job of introducing new features, writing documentation for them, as well as adjusting and improving the already existing base.

Numbers


What can I say about the new release? As planned, Symfony 2.2 took 6 months and consists of 711 pull requests containing 2,035 commits submitted by 44 developers (47,191 additions and 13,512 deletions), the documentation received 1,312 commits from 41 authors (13,038 additions and 3,336 deletions).

The result was 2035 commits and 711 pull requests for 6 months, that is, an average of 11 commits and 4 pull requests every day.

New opportunities


The numbers are not so interesting when it comes to improvement, so what about the new features and major changes? I would not like to list them, since a lot has been said about them in this blog over the past few months:
')


Symfony 2.2 is also introduced with two new components that were extracted from existing code:


Documentation


The documentation team has done the hardest work, and all the new features are already documented, and interesting recipes are presented in our cookbook .

Upgrade to version 2.2


Up the version from 2.1 to 2.2 was quite simple and without unnecessary trouble according to reviews from Twitter
Update your composer.json and close the composer.phar update:
composer.json
diff --git a/composer.json b/composer.json index 8f905d7..c2d7588 100644 --- a/composer.json +++ b/composer.json @@ -6,18 +6,18 @@ }, "require": { "php": ">=5.3.3", - "symfony/symfony": "2.1.*", - "doctrine/orm": ">=2.2.3,<2.4-dev", - "doctrine/doctrine-bundle": "1.0.*", + "symfony/symfony": "2.2.*", + "doctrine/orm": "~2.2,>=2.2.3", + "doctrine/doctrine-bundle": "1.2.*", "twig/extensions": "1.0.*", "symfony/assetic-bundle": "2.1.*", - "symfony/swiftmailer-bundle": "2.1.*", - "symfony/monolog-bundle": "2.1.*", - "sensio/distribution-bundle": "2.1.*", - "sensio/framework-extra-bundle": "2.1.*", - "sensio/generator-bundle": "2.1.*", - "jms/security-extra-bundle": "1.2.*", - "jms/di-extra-bundle": "1.1.*" + "symfony/swiftmailer-bundle": "2.2.*", + "symfony/monolog-bundle": "2.2.*", + "sensio/distribution-bundle": "2.2.*", + "sensio/framework-extra-bundle": "2.2.*", + "sensio/generator-bundle": "2.2.*", + "jms/security-extra-bundle": "1.4.*", + "jms/di-extra-bundle": "1.3.*" }, "scripts": { "post-install-cmd": [ @@ -36,9 +36,12 @@ "config": { "bin-dir": "bin" }, - "minimum-stability": "dev", + "minimum-stability": "alpha", "extra": { "symfony-app-dir": "app", - "symfony-web-dir": "web" + "symfony-web-dir": "web", + "branch-alias": { + "dev-master": "2.2-dev" + } } } 


Then, read the upgrade documentation carefully and do what it says (you may also need to read the upgrade instructions for Symfony Standard Edition).
Additionally, you can also make some changes to make your application more compatible with symfony 3.0.

Installation


If you are starting a new project using symfony 2.2, you have several options:

If you use some symfony components in your new application, use version 2.2.0 or branch 2.2:


What's next?


So what next? Judging by the development process, Symfony 2.3 will be released at the end of May 2013 and will be the first version with long-term support . This version will also be used by Drupal 8 and Laravel 4, and these are just a couple of project names that rely on Symfony Components.

Thank you for continuing to support symfony.

Source: https://habr.com/ru/post/171251/


All Articles