diff options
| author | Emmanuel <e.beltranfs@gmail.com> | 2017-07-24 12:33:30 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2017-07-24 14:11:32 -0400 |
| commit | b6620dee72dc44da45403ff663853bfd8421c63e (patch) | |
| tree | d37bb50aa8c23bbace33a92c456df4b73c80b5a3 /docs | |
| parent | aef117eb2e7805c5965adbfbfe1b5374cb58bbbe (diff) | |
[1.11.x] Fixed #28349 -- Doc'd how to upgrade Django from LTS to LTS.
Backport of 27ef04bb5c3118e00d3eda4b3aa3201d18ea1785 from master
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/howto/upgrade-version.txt | 8 |
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 ============ |