Update release guide upon website update steps

src/site/markdown/release-guide.md

@@ -216,17 +216,6 @@ and serve no purpose and can be deleted.
 Remove `rugged-X.Y.source-jar*` since they are duplicates of the
 `rugged-X.Y-sources.jar*` artifacts. Then click the “Close” button.
 
-## Update Rugged version in Rugged test website
-
-One edit needs to be made to the Rugged website before calling the vote. Fetch the current code:
-
-    git clone https://gitlab.orekit.org/orekit/website-2015
-
-Switch to `develop` branch and edit `_data/rugged/versions.yml` by adding the new version X.Y 
-to the list. 
-
-Once the modification pushed to develop branch, the [test website](https://test.orekit.org/rugged) will be updated
-
 ## Calling for the vote
 
 Everything is now ready so the developers and PMC can vote for the release.
@@ -344,22 +333,32 @@ Github automically adds two assets (zip and tarball archives of the tagged sourc
 ## Update Rugged website
 
 Several edits need to be made to the Rugged website after the vote.
+Fetch the current code:
+
+    git clone https://gitlab.orekit.org/orekit/website-2015
+
+Switch to `develop` branch. 
+
+<!-- Edit `download/.htaccess` and replace the URLs of the 3 Rugged artifacts with the ones used to create the release notes.-->
+
+<!-- Edit `_layouts/home_rugged.html` and edit the text of the button to use the new version.-->
 
-Edit `download/.htaccess` and replace the URLs of the 3 Rugged artifacts
-with the ones used to create the release notes.
+Edit `rugged/overview.html` with the new Orekit and Hipparchus versions. 
+Don't forget to update the `rugged/img/rugged-architecture.png` image with the new dependencies.
 
-Edit `_layouts/home_rugged.html` and edit the text of the button to use the new version.
+Create a new post for the release in `_post/` using as template a previous Rugged post (in order to be published in the Rugged News page). 
 
-Edit `rugged/overview.html` with the new Orekit and Hipparchus versions. Don't forget to update the
-rugged/img/rugged-architecture.png image with the new dependencies.
 
-Create a new post for the release in `_post/` using as template a previous Rugged post (in order to be published in the Rugged News page). To be noticed the `--future` option is needed to see a post in the future, otherwise `jekyll serve` will ignore it !
+<!-- To be noticed the `--future` option is needed to see a post in the future, otherwise `jekyll serve` will ignore it ! -->
+<!-- Run:-->
+<!--    jekyll serve --future-->
+<!-- and make sure the website looks nice. View it on http://localhost:4000/-->
 
-Run:
 
-    jekyll serve --future
+Once the modification pushed to develop branch, wait the pipeline on Gitlab is finished, then the [test website](https://test.orekit.org/rugged) will be updated.
 
-and make sure the website looks nice. View it on http://localhost:4000/
+Once the modification validated, merge the develop branch into the master branch and pushed the master branch. 
+Once the  pipeline on Gitlab is finished, then the [website](https://www.orekit.org/rugged) will be updated.
 
 ## Close X.Y milestone