From 8bdd24b35e3d86fa9e0e0c41de799a5c0c3de0c8 Mon Sep 17 00:00:00 2001 From: Javier Eguiluz Date: Thu, 1 Sep 2016 16:36:19 +0200 Subject: [PATCH 1/3] Mentioned the "Symfony Upgrade Fixer" in the upgrade article --- setup/upgrade_major.rst | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/setup/upgrade_major.rst b/setup/upgrade_major.rst index 5aedda06b5a..971e6c3ae8e 100644 --- a/setup/upgrade_major.rst +++ b/setup/upgrade_major.rst @@ -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 +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*. @@ -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 @@ -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 From 80733b590066e9ed4753cb8ada5a85d3ee56825d Mon Sep 17 00:00:00 2001 From: Javier Eguiluz Date: Mon, 5 Sep 2016 08:29:59 +0200 Subject: [PATCH 2/3] Fixed a minor grammar issue --- setup/upgrade_major.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/setup/upgrade_major.rst b/setup/upgrade_major.rst index 971e6c3ae8e..b3a95f94249 100644 --- a/setup/upgrade_major.rst +++ b/setup/upgrade_major.rst @@ -5,9 +5,9 @@ Upgrading a Major Version (e.g. 2.7.0 to 3.0.0) =============================================== 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 -backwards compatibility. However, Symfony makes this upgrade process as smooth -as possible. +changes). These releases are the trickiest to upgrade, as they are allowed to +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 actually released. This is called making your code *future compatible*. From abd9a42ccae401d86742950ff287f21dc9ab2ba1 Mon Sep 17 00:00:00 2001 From: Javier Eguiluz Date: Sun, 18 Sep 2016 12:53:02 +0200 Subject: [PATCH 3/3] Minor reword --- setup/upgrade_major.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/setup/upgrade_major.rst b/setup/upgrade_major.rst index b3a95f94249..19cd041ff0d 100644 --- a/setup/upgrade_major.rst +++ b/setup/upgrade_major.rst @@ -116,8 +116,8 @@ done! .. 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. + `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: