Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions setup/upgrade_major.rst
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,9 @@
Upgrading a Major Version (e.g. 2.7.0 to 3.0.0)
===============================================

Every few years, Symfony releases a new major version release (the first number
Every two years, Symfony releases a new major version release (the first number
changes). These releases are the trickiest to upgrade, as they are allowed to
contain BC breaks. However, Symfony tries to make this upgrade process as
break backwards compatibility. However, Symfony makes this upgrade process as
smooth as possible.

This means that you can update most of your code before the major release is
Expand Down Expand Up @@ -113,6 +113,12 @@ done!

(you can also execute the command like ``SYMFONY_DEPRECATIONS_HELPER=weak phpunit``).

.. tip::

Some members of the Symfony Community have developed a tool called
`Symfony-Upgrade-Fixer`_ which automatically fixes some of the most common
deprecations found when upgrading from Symfony 2 to Symfony 3.

.. _upgrade-major-symfony-composer:

2) Update to the New Major Version via Composer
Expand Down Expand Up @@ -152,3 +158,5 @@ There is a good chance that you're done now! However, the next major version
Make sure you read the ``UPGRADE-X.0.md`` (where X is the new major version)
included in the Symfony repository for any BC break that you need to be aware
of.

.. _`Symfony-Upgrade-Fixer`: https://github.com/umpirsky/Symfony-Upgrade-Fixer