diff --git a/.gitlab/issue_templates/release.md b/.gitlab/issue_templates/release.md
index 5f7441d580c7c1a808d98f3cfe5fb16f0d790f45..fce450b8453dea9babc99fb33f604ed9faa10f89 100644
--- a/.gitlab/issue_templates/release.md
+++ b/.gitlab/issue_templates/release.md
@@ -8,7 +8,6 @@ We are ready to release OTB version MAJOR.MINOR.PATCH. The following steps need
 
 ### 2. Housekeeping
 * [ ] In this story, make a list of blocking issues for the release (if any)
-* [ ] [Update dashboard scripts](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#dashboard) to support new version numbers
 * [ ] [Update the SuperBuild archive](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#superbuild-archive) (if needed)
 * [ ] Update release notes (walk the GitLab MR merged history and log all improvements)
 * [ ] Update the date in RELEASE_NOTES.txt
@@ -31,9 +30,8 @@ Once all blocking issues are closed, and the previous steps are done:
 
 ### 4. Publish and plan next release
 * [ ]   [Prepare and upload source packages](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#prepare-and-upload-source-packages)
-* [ ]   [Promote nightly packages](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#promote-nightly-packages)
+* [ ]   [Promote staging packages](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#promote-staging-packages)
 * [ ]   [Update documentation](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#update-documentation)
-    * [ ] Software Guide
     * [ ] Cookbook
     * [ ] Doxygen
     * [ ] WordPress page "Home" and "Download" pages
@@ -43,7 +41,6 @@ Once all blocking issues are closed, and the previous steps are done:
 * [ ] Announcement on social networks (twitter, google+)
 * [ ] Forward announcement to news_item@osgeo.org ([OSGeo news](https://www.osgeo.org/foundation-news/))
 * [ ] Plan the next release (nominate new release manager, setup PSC meeting on IRC)
-* [ ] Contact QGis processing plugin maintainer to update XML description for new OTB-Applications (or [supply it](https://wiki.orfeo-toolbox.org/index.php/QGIS_access_to_OTB_applications#updating-the-XML-descriptors))
 * [ ] Remove public branches related to MR or bugfix merged before the release
 
 /label ~story
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 67732a9168fd3a2bc4601113c7118284bb96adff..0ab1c1c290979cb79a6b393faa0f48f9b913eef6 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -107,27 +107,21 @@ OTB team.
 
 ### Using the CI platform
 
-The CI pipelines are triggered automatically when pushing commits. If you push
-to a fork, you will need a few settings to trigger properly the CI pipelines:
-
-* You must add Runners for your fork: the best way is to ask access to the
-  runners from main repository when doing your first MR. During code review,
-  someone from CI admins will assign the runners to your fork.
-* [Optional] You can create a
-  [personal access token](https://docs.gitlab.com/ce/user/profile/personal_access_tokens.html)
-  (choose the scope API) and add it as a secret variable: on the project page of
-  your fork, go to Settings -> CI/CD -> Variables, add the variable `K8S_SECRET_API_TOKEN`
-  with your token as value (you should mask this variable for security reasons).
+There isn't much to do in order to use the CI platform. The CI pipelines are
+triggered automatically when pushing commits. However, if you push to a fork,
+you will first need an access to the Runners from main repository. You
+can request it when doing your first MergeRequest. During code review, someone
+from CI admins will assign the runners to your fork.
 
 When your pipeline ends, there are two cases:
 
 * if all the jobs succeed, you see a green pipeline, which means no problem was
   found on your commit.
 * if one job fails, you see a red pipeline, which means something is broken in
-  your commit. The pipeline widget on Gitlab will tell you which job failed. You
-  will also find special jobs "cdash:..." in the stage `external` that provide
-  a link to the [Dashboard](https://cdash.orfeo-toolbox.org/index.php?project=OTB)
-  where you can look more in details into compilation errors and failed tests.
+  your commit. The pipeline widget on Gitlab will tell you which job failed, so
+  you can check the logs. There, you may also find links to
+  [CDash](https://cdash.orfeo-toolbox.org/index.php?project=OTB) submissions
+  where compilation errors and failed test can be investigated more easily.
 
 More details on the CI platform can be found
 [here](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/OTB-Continuous-Integration-platform).