Skip to content
Snippets Groups Projects
Commit 3fe999c5 authored by Sören Henning's avatar Sören Henning
Browse files

Update release process

parent b173f32f
No related branches found
No related tags found
1 merge request!84Gitlab CI for Theodolite-Kotlin-Quarkus
Pipeline #1836 skipped
......@@ -6,18 +6,19 @@ nav_order: 2
# Release Process
We assume that we are creating the release `v0.1.1`. Please make sure to adjust
This document describes how to perform a new Theodolite release.
We assume that we are creating the release `v0.3.1`. Please make sure to adjust
the following steps according to the release, you are actually performing.
1. Create a new branch `v0.1` if not already exists. This branch will never
1. Create a new branch `v0.3` if it does not already exists. This branch will never
again be merged into master.
2. Checkout the `v0.1` branch.
2. Checkout the `v0.3` branch.
3. Update all references to Theodolite Docker images to tag `v0.1.1`. These are
mainly the Kubernetes resource definitions in `execution` as well as the Docker
Compose files in `docker-test`.
3. Update all references to Theodolite Docker images to tag `v0.1.1`. These are the Kubernetes resource definitions in
`execution`, the Docker Compose files in `docker-test` and the example `theodolite.yaml` job.
4. Commit these changes.
5. Tag this commit with `v0.1.1`. The corresponding Docker images will be uploaded.
5. Tag this commit with `v0.3.1`. The corresponding Docker images will be uploaded.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment