merge_request_templates: Release, details, move deploy part

.gitlab/merge_request_templates/Release (vidjil-algo).md

 
-## Preparation
+## Before the release
+
+### Documentation
 
 * [ ] New features are described in `doc/vidjil-algo.md`
-* [ ] Breaking changes (or needed) are understood
+* [ ] Breaking changes (and needed configuration changes) are understood
  
 On the `feature-a/release` branch, the last commit is the release commit updating the three following files:
  * [ ] CHANGELOG
  * [ ] `doc/vidjil-algo.md` with the proper release tag
  * [ ] `algo/release` with the proper release tag
 
-## Pipelines
+### Pipelines
 
 https://gitlab.inria.fr/vidjil/vidjil/pipelines/XXXXX
+(if tests passed on different pipelines, indicate below the relevant pipelines)
 
 Usual tests should pass, but also:
 * [ ] prepare_release
@@ -23,21 +26,21 @@ Benchmarks
 * [ ] almost no change...
 * [ ] ... or significant changes are understood
 
-## Tag and push
+## The release, publish, tag and push
+
+* [ ] merge this MR to *master* and tag: `git tag release-20XX-XX` 
+* [ ] push: `git push origin master release-20XX-XX`
+* [ ] mirror to GH: `git push github master release-20XX.XX`
+* [ ] click `publish_release` (there may be changes to CD...)
+* [ ] deploy the doc
+
 
-* [ ] tag (`git tag release-20XX-XX; git push origin release-20XX-XX`)
-* [ ] mirror to GH
+After these steps, we merge back the release in `dev`:
+* [ ] merge this MR to dev
 
-## Deploy
+## After the release: deploy
 
-* [ ] doc 
-* [ ] `app` (vidjil-algo-next)
-* [ ] `app` if needed, update server configs
-* [ ] `app` notification to users
-* [ ] `app` (vidjil-algo)
-* [ ] `app` test on production (X5 and L4)
-* [ ] `hds` queue for qualification ?
-* [ ] twice a year, communicate to users
+* [ ] Open a new internal issue with the `Deploy (vidjil-algo)` template.
 
 /label ~cpp