Skip to content

Update upgrade_major.rst #9882

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

Merged
merged 1 commit into from
Jun 6, 2018
Merged

Update upgrade_major.rst #9882

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 3 additions & 3 deletions setup/upgrade_major.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
.. index::
single: Upgrading; Major Version

Upgrading a Major Version (e.g. 3.4.0 to 4.0.0)
Upgrading a Major Version (e.g. 3.4.0 to 4.1.0)
===============================================

Every two years, Symfony releases a new major version release (the first number
Expand Down Expand Up @@ -30,7 +30,7 @@ backwards incompatible changes. To accomplish this, the "old" (e.g. functions,
classes, etc) code still works, but is marked as *deprecated*, indicating that
it will be removed/changed in the future and that you should stop using it.

When the major version is released (e.g. 4.0.0), all deprecated features and
When the major version is released (e.g. 4.1.0), all deprecated features and
functionality are removed. So, as long as you've updated your code to stop
using these deprecated features in the last version before the major (e.g.
3.4.*), you should be able to upgrade without a problem.
Expand Down Expand Up @@ -128,7 +128,7 @@ Composer by modifying your ``composer.json`` file:
"...": "...",

"require": {
"symfony/symfony": "^4.0",
"symfony/symfony": "^4.1",
},
"...": "..."
}
Expand Down