aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorG. Ann Campbell <ann.campbell@sonarsource.com>2018-10-17 08:54:39 -0400
committerSonarTech <sonartech@sonarsource.com>2018-10-17 20:20:51 +0200
commitd9aea65ee88097157ae3dea739eb9daab7719787 (patch)
treea0abc9ade41677f63def187b939b6f5dc7d1e62e
parentb86a966bd1a06f5785a1fd7f3bf5c5fe0ae3004c (diff)
downloadsonarqube-d9aea65ee88097157ae3dea739eb9daab7719787.tar.gz
sonarqube-d9aea65ee88097157ae3dea739eb9daab7719787.zip
amend multi-version upgrade statement
-rw-r--r--server/sonar-docs/src/pages/setup/upgrading.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/server/sonar-docs/src/pages/setup/upgrading.md b/server/sonar-docs/src/pages/setup/upgrading.md
index 88d862c30f7..aaadf712d07 100644
--- a/server/sonar-docs/src/pages/setup/upgrading.md
+++ b/server/sonar-docs/src/pages/setup/upgrading.md
@@ -4,7 +4,7 @@ url: /setup/upgrading/
---
<!-- sonarqube -->
-Upgrading across multiple versions is handled automatically. However, if in your migration path you have an LTS version, you must first migrate to this LTS and then migrate to your target version.
+Upgrading across multiple, non-LTS versions is handled automatically. However, if in your migration path you have an LTS version, you must first migrate to this LTS and then migrate to your target version.
Example 1 : 5.1 -> 7.0, migration path is 5.1 -> 5.6.7 LTS -> 6.7.x LTS -> 7.0
Example 2 : 6.2 -> 6.7, migration path is 6.2 -> 6.7.x LTS (where x is the latest patch available for 6.7 - you don't need to install all the intermediary patches, just take the latest)