finish 4.0 upgrade doc & cli

README.md

@@ -44,7 +44,7 @@ We provide a semi-automatic way to proceed to ``4.0`` upgrade not to break old i
 # be sure to be on the latest changeset of the corpusops.bootstrap's local branch checkout
 cd $corpusops_bootstrap && \
     git fetch origin && \
-    ./bin/install.sh -C -b 4.0 --ansible-branch 2.17 && \
+    ./bin/install.sh -C -b 4.0 --ansible-branch 2.17 --roles-branch 4.0 && \
     bin/install.sh -C && \
     rm -f .corpusops/*_branch
 ```

bin/install.sh

@@ -1620,6 +1620,7 @@ usage() {
     bs_help "    -u|--use-venv yes/no" "do we use venv" "$(get_corpusops_use_venv)" y
     bs_help "    --ansible-url <url>" "ansible fork git url" "$(get_ansible_url)" y
     bs_help "    --ansible-branch <branch>" "ansible fork git branch" "$(get_ansible_branch)" y
+    bs_help "    --roles-branch <branch>" "corpusops ansible roles git branch" "$(get_corpusops_roles_branch)" y
     bs_help "    -C|--no-confirm" "Do not ask for start confirmation" "" y
     bs_help "    --no-colors" "No terminal colors" "${NO_COLORS}" y
     bs_help "    -d|--debug" "activate debug" "${DEBUG}" y
@@ -1723,6 +1724,9 @@ parse_cli_opts() {
         if [ "x${1}" = "x--ansible-branch" ]; then
             ANSIBLE_BRANCH="${2}";sh="2";argmatch="1"
         fi
+        if [ "x${1}" = "x--roles-branch" ]; then
+            CORPUSOPS_ROLES_BRANCH="${2}";sh="2";argmatch="1"
+        fi
         if [ "x${1}" = "x--upgrade" ]; then
             DO_UPGRADE="1";argmatch="1"
         fi