summaryrefslogtreecommitdiff
path: root/docs/howto
diff options
context:
space:
mode:
authorEmmanuel <e.beltranfs@gmail.com>2017-07-24 12:33:30 -0500
committerTim Graham <timograham@gmail.com>2017-07-24 13:33:30 -0400
commit27ef04bb5c3118e00d3eda4b3aa3201d18ea1785 (patch)
treefac337e99415d23e7980ff9a1f0e67236f66fe1b /docs/howto
parentf9e5f9ae9f83c7ddf5e5d3c369b6bf54a9b80ab5 (diff)
Fixed #28349 -- Doc'd how to upgrade Django from LTS to LTS.
Diffstat (limited to 'docs/howto')
-rw-r--r--docs/howto/upgrade-version.txt8
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/howto/upgrade-version.txt b/docs/howto/upgrade-version.txt
index 9f433094b1..c495bd79e5 100644
--- a/docs/howto/upgrade-version.txt
+++ b/docs/howto/upgrade-version.txt
@@ -33,6 +33,14 @@ the new Django version(s):
Pay particular attention to backwards incompatible changes to get a clear idea
of what will be needed for a successful upgrade.
+If you're upgrading through more than one feature version (e.g. A.B to A.B+2),
+it's usually easier to upgrade through each feature release incrementally
+(A.B to A.B+1 to A.B+2) rather than to make all the changes for each feature
+release at once. For each feature release, use the latest patch release (A.B.C).
+
+The same incremental upgrade approach is recommended when upgrading from one
+LTS to the next.
+
Dependencies
============