docs: update README on release procedure

README.md

@@ -11,14 +11,14 @@ See also [developers documentation](DEVELOPERS.md) (in french)
  * python3
  * pandoc ^2 (optional, for PDF documentation only)
  * texlive (optional, for PDF documentation only)
- 
+
 Building the HTML documentation requires MkDocs and some extensions:
 
 ```sh
 sudo apt install python3-pip python3-setuptools
 python3 -m pip install mkdocs python-markdown-math mkdocs-material
 ```
- 
+
 Building the PDF documentation requires pandoc and a LaTeX distribution (for ex. texlive) with a few packages:
 
 ```sh
@@ -225,7 +225,7 @@ npm install -g tsviz
 ```
 
 There's currently a bug on debian like distribution due to a wrong declaration of graphviz path in the code: https://github.com/joaompneves/tsviz/issues/5
-As a workaround, you can create a link to the right path: `sudo ln -s /usr/bin/dot /usr/local/bin/dot` 
+As a workaround, you can create a link to the right path: `sudo ln -s /usr/bin/dot /usr/local/bin/dot`
 
 To draw the diagram:
 ```sh
@@ -251,11 +251,11 @@ sudo find /usr/lib/node_modules/protractor -regextype sed -regex "^.*/chromedriv
 
 Use [semantic versioning](https://semver.org/).
 
-**It's discouraged to execute release steps manually, see Release Script below**
+**It's discouraged to execute release steps manually, skip this section and see Release Script below**
 
 Before releasing a new stable version, a new version of JaLHyd should be tagged, see "Release Policy" in [JaLHyd's README.md](https://gitlab.irstea.fr/cassiopee/jalhyd/blob/master/README.md)
 
-Then, one should complete the following files
+Then, one should complete the following files:
  - `CHANGELOG.md`
  - `package.json` (update "version", or use `npm version`)
  - `jalhyd_branch` (be sure that it contains "master" or is empty)
@@ -270,12 +270,16 @@ The `stable` tag should be set **before** the version tag, so that `git describe
 
 **Important:** the release script assumes that you run it from the current nghyd source directory `nghyd`, and that JaLHyd source directory `jalhyd` is present at the same level.
 
+Before running the script:
+ * update `CHANGELOG.md` in both JaLHyd and NgHyd
+ * set the content of `jalhyd_branch` to "master"
+
 This script:
  * checks out "master" branch of JaLHyd, pulls the latest changes, installs dependencies, runs unit tests, commits changes if any
- * updates JaLHyd version, commits changes
+ * updates JaLHyd version in `package.json`, commits changes
  * creates the right tags for JaLHyd and pushes them
  * checks out "master" branch of NgHyd, pulls the latest changes, installs dependencies, commits changes if any
- * updates NgHyd version, commits changes
+ * updates NgHyd version in `package.json`, commits changes
  * creates the right tags for NgHyd and pushes them
 
 It **does not** check that `jalhyd_branch` is OK nor that `jalhyd/CHANGELOG.md` and `nghyd/CHANGELOG.md` are up to date, but reminds you to do it.