[PATCH 4 of 6] docs: upgrade: front-end should be built for all installation methods

[Thomas De Schampheleire]

# HG changeset patch
# User Thomas De Schampheleire <thomas.de_schampheleire at nokia.com>
# Date 1546033429 -3600
#      Fri Dec 28 22:43:49 2018 +0100
# Node ID c9b121231e8000ca300c2fcfbce61caaa5c1a933
# Parent  06c1bfe5ca8117733d40dc31a2e6336299bd9683
docs: upgrade: front-end should be built for all installation methods

... and not exclusively when installing from version control.

diff --git a/docs/upgrade.rst b/docs/upgrade.rst
--- a/docs/upgrade.rst
+++ b/docs/upgrade.rst
@@ -90,7 +90,6 @@ private changes (in which case you shoul
     hg update
     hg parent   # make a note of the new revision
     pip install --upgrade -e .
-    kallithea-cli front-end-build
 
 .. _upgrade_config:
 
@@ -175,7 +174,17 @@ need to append the following lines to it
 Your config file should now work with Alembic.
 
 
-7. Update Git repository hooks
+7. Prepare the front-end
+------------------------
+
+Starting with Kallithea 0.4, external front-end dependencies are no longer
+shipped but need to be downloaded and/or generated at installation time. Run the
+following command::
+
+    kallithea-cli front-end-build
+
+
+8. Update Git repository hooks
 ------------------------------
 
 It is possible that an upgrade involves changes to the Git hooks installed by
@@ -193,15 +202,15 @@ To update the hooks of your Git reposito
     not necessary if you only have Mercurial repositories.
 
 
-8. Rebuild the Whoosh full-text index
+9. Rebuild the Whoosh full-text index
 -------------------------------------
 
 It is recommended that you rebuild the Whoosh index after upgrading since
 new Whoosh versions can introduce incompatible index changes.
 
 
-9. Start the Kallithea web application
---------------------------------------
+10. Start the Kallithea web application
+---------------------------------------
 
 This step once again depends entirely on the web server software used to
 serve Kallithea.