innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

[3.0.x] Made examples concrete in upgrade documentation. 

Backport of e4bc4f26b2 from master
This commit is contained in:
Adam Johnson 2020-01-21 12:02:14 +00:00 committed by Mariusz Felisiak
parent 789de6050a
commit a062d432a3
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/howto/upgrade-version.txt
View File

@ -33,10 +33,11 @@ the new Django version(s):
Pay particular attention to backwards incompatible changes to get a clear idea Pay particular attention to backwards incompatible changes to get a clear idea
of what will be needed for a successful upgrade. 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), If you're upgrading through more than one feature version (e.g. 2.0 to 2.2),
it's usually easier to upgrade through each feature release incrementally 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 (2.0 to 2.1 to 2.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). release at once. For each feature release, use the latest patch release (e.g.
for 2.1, use 2.1.15).
The same incremental upgrade approach is recommended when upgrading from one The same incremental upgrade approach is recommended when upgrading from one
LTS to the next. LTS to the next.