From 27841fbd8aeb0f8e8bb9a9d4b7d2e3eb19daa4ff Mon Sep 17 00:00:00 2001
From: Gael Yvert <Gael.Yvert@ens-lyon.fr>
Date: Tue, 28 Jan 2025 13:31:15 +0100
Subject: [PATCH] more dev doc

---
 doc/dev/README.md | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/doc/dev/README.md b/doc/dev/README.md
index 7c14130..2c91707 100755
--- a/doc/dev/README.md
+++ b/doc/dev/README.md
@@ -139,6 +139,9 @@ Steps when making a beta-release:
 - commit your changes
 - merge to the master branch. For simplicity/clarity of this project, we don't want too many branches and things will be much simpler if all releases are on the master branch. 
 - Make a tag with a new version in format `vX.X.X-beta`
+```sh
+git tag -a vX.X.X-beta -m "version X.X.X-beta" # change with tag name of the new version
+```
 - Produce the release on Gitlab server. Indicate in **comments that it is a beta release**, and link it to milestones and any relevant information.
 - Update branch beta-release
 ```sh
@@ -158,7 +161,15 @@ When releasing a stable-release:
 ```
 - commit your changes
 - merge to the master branch.
-- Make a tag with a new version in format `vZ.Z.Z`
+- Make a tag with a new version in format `vZ.Z.Z` # change with tag name of the new version
+```sh
+git tag -a vZ.Z.Z -m "version Z.Z.Z"
+```
+- Produce the release on Gitlab server. Indicate in **comments that it is a beta release**, and link it to milestones and any relevant information.
+- Update branch beta-release
+```sh
+git checkout latest-beta
+git 
 - Produce the release on Gitlab server. Indicate in **comments that it is a stable release**, and link it to milestones and any relevant information.
 - Update branch latest-release:
 ```sh
-- 
GitLab