From 086355f72de917fd1b5305231c48ecaff6199ddd Mon Sep 17 00:00:00 2001
From: florian <f.spreckelsen@inidscale.com>
Date: Tue, 31 May 2022 13:41:44 +0200
Subject: [PATCH] DOC: Add integration tests to release guidelines
---
RELEASE_GUIDELINES.md | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/RELEASE_GUIDELINES.md b/RELEASE_GUIDELINES.md
index 59c2fab..c725ec8 100644
--- a/RELEASE_GUIDELINES.md
+++ b/RELEASE_GUIDELINES.md
@@ -13,16 +13,19 @@ guidelines of the CaosDB Project
## Steps
-1. Create a release branch from the dev branch. This prevents further changes
- to the code base and a never ending release process. Naming: `release-<VERSION>`
+1. Create a release branch from the dev branch. This prevents further changes to
+ the code base and a never ending release process. Naming:
+ `release-<VERSION>`. Also create a branch with the same name in cppinttests.
2. Update CHANGELOG.md
3. Check all general prerequisites.
4. Update version numbers:
- 1. In [CMakeLists.txt](./CMakeLists.txt): Check the `MAJOR`, `MINOR`, `PATCH` version variables.
+ 1. In [CMakeLists.txt](./CMakeLists.txt): Check the version variables and
+ make sure that the compatible caosdb-server version is set correctly.
2. In `conanfile.py`: Update the `version` variable.
+ 3. In `caosdb-cppinttest/conanfile.py`: Update the version
5. Merge the release branch into the main branch.
@@ -37,4 +40,5 @@ guidelines of the CaosDB Project
9. Release cppinttests with updated cpplib version
-10. Merge `main` back into `dev` and increase patch version by one to begin next release cycle.
+10. Merge `main` back into `dev` and increase patch version by one to begin next
+ release cycle. Do the same in cppintest.
--
GitLab