style(help): added a test step
@@ -8,14 +8,16 @@ A PATCH version contains only fixes to functionality that already existed.
A MINOR version contans new features, and fixes to functionality that already existed.
-Every MAJOR version (e.g. 7.0.0, 8.0.0, etc.) contains breaking changes. These breaking changes may not affect every user, but every user needs to check to see whether and how they to change the way they call [solution_name] before upgrading to the next MAJOR version. To do this check and and upgrade to the next MAJOR version:
+Every MAJOR version (e.g. 7.0.0, 8.0.0, etc.) contains breaking changes. These breaking changes may not affect every user, but every user needs to check to see whether and how they to change the way they call [solution_name] before upgrading to the next MAJOR version. To do this check and and upgrade to the next MAJOR version: In a test environment:
1. Upgrade to the latest MINOR.PATCH [solution_name] version available for the MAJOR version you are currently running. Read all of the deprecation messages and the upgrade guidance they provide, and change the way you are calling [solution_name] until all deprecation messages are gone. Read all of the documentation for the new properties you are using, and all of the documentation relevant to the features they control.
2. Upgrade to the next MAJOR version.
+3. Test.
You must do this one MAJOR version at a time (do not skip over a MAJOR version).
-For example, suppose you are running 7.12.1, and you want to upgrade to 8.0.0:
+For example, suppose you are running 7.12.1, and you want to upgrade to 8.0.0: In a test environment:
1. Upgrade to 7.14.0 (the latest 7.y.z version available). Read all of the deprecation messages and the upgrade guidance they provide, and change the way you are calling [solution_name] until all deprecation messages are gone. Read all of the documentation for the new properties you are using, and all of the documentation relevant to the features they control.
2. Upgrade to 8.0.0.
+3. Test.
