From e4bc4f26b27122f5887a5eea811ff985d9ab8b8d Mon Sep 17 00:00:00 2001 From: Adam Johnson Date: Tue, 21 Jan 2020 12:02:14 +0000 Subject: [PATCH] Made examples concrete in upgrade documentation. --- docs/howto/upgrade-version.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/howto/upgrade-version.txt b/docs/howto/upgrade-version.txt index 9ce0be2b16..007df6459c 100644 --- a/docs/howto/upgrade-version.txt +++ b/docs/howto/upgrade-version.txt @@ -33,10 +33,11 @@ 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), +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 -(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). +(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 (e.g. +for 2.1, use 2.1.15). The same incremental upgrade approach is recommended when upgrading from one LTS to the next.