From 1c083ba7bccba9fc369530fe3ad70c5a1578e8a8 Mon Sep 17 00:00:00 2001
From: Jesse Haka <haka.jesse@gmail.com>
Date: Fri, 6 Sep 2024 16:27:41 +0300
Subject: [PATCH] fix instructions

---
 docs/release-procedure.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/docs/release-procedure.md b/docs/release-procedure.md
index f0e60bf262..13b031418b 100644
--- a/docs/release-procedure.md
+++ b/docs/release-procedure.md
@@ -31,11 +31,12 @@ critical bug fixes.
 4. Once the PR is merged, make a tag and push it to the upstream repository.
 
     ```bash
-    $ git checkout -b release-X.Y upstream master
-    $ git pull upstream release-X.Y --tags
-    $ git tag -m "Release for cloud-provider-openstack to support Kubernetes release x" vX.Y.Z
+    $ git checkout master
+    $ git pull upstream master
+    $ git tag vX.Y.Z
     $ git push upstream vX.Y.Z
-    $ git push upstream release-X.Y
+    $ git checkout -b release-X.Y
+    $ git push origin release-X.Y
     ```
 
 5. [Github Actions](https://github.com/kubernetes/cloud-provider-openstack/actions/workflows/release-cpo.yaml) will create new [Docker images](https://console.cloud.google.com/gcr/images/k8s-staging-provider-os) and generate a [new draft release](https://github.com/kubernetes/cloud-provider-openstack/releases) in the repository.