Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Mentioned the "Symfony Upgrade Fixer" in the upgrade article #6941

Merged
merged 3 commits into from
Sep 19, 2016
Merged

Mentioned the "Symfony Upgrade Fixer" in the upgrade article #6941

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8bdd24b
Mentioned the "Symfony Upgrade Fixer" in the upgrade article
javiereguiluz Sep 1, 2016
80733b5
Fixed a minor grammar issue
javiereguiluz Sep 5, 2016
abd9a42
Minor reword
javiereguiluz Sep 18, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 12 additions & 4 deletions setup/upgrade_major.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,10 @@
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
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
smooth as possible.
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 break
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

allowed to break backwards compatibility

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
actually released. This is called making your code *future compatible*.
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 fixes some of the most common deprecations
automatically and can save you a lot of work.

.. _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