From 610020bb96e9890b293cfba450f2d41b846bc905 Mon Sep 17 00:00:00 2001
From: Timm Fitschen <t.fitschen@indiscale.com>
Date: Wed, 25 Oct 2023 21:54:19 +0200
Subject: [PATCH] DOC: update RELEASE_GUIDELINES

---
 RELEASE_GUIDELINES.md | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/RELEASE_GUIDELINES.md b/RELEASE_GUIDELINES.md
index a5eeca1..584227a 100644
--- a/RELEASE_GUIDELINES.md
+++ b/RELEASE_GUIDELINES.md
@@ -19,10 +19,15 @@ guidelines of the CaosDB Project
 
 2. Check all general prerequisites.
 
+3. Assure that the latest patch actually updates the CaosDBVersion() procedure
+   and that the version matches the version you are about to release.
+
 4. Merge the release branch into the main branch.
 
-5. Tag the latest commit of the main branch with `v<VERSION>`.
+5. Wait for the main branch pipeline to pass.
+
+6. Tag the latest commit of the main branch with `v<VERSION>`.
 
-6. Delete the release branch.
+7. Delete the release branch.
 
-7. Merge the main branch back into the dev branch.
+8. Merge the main branch back into the dev branch.
-- 
GitLab