From 9c3195c39f5b4e2b685c349661ea325067d713ad Mon Sep 17 00:00:00 2001
From: gprat <guylaine.prat@c-s.fr>
Date: Tue, 21 Jul 2020 08:28:27 +0200
Subject: [PATCH] Complete release guide
---
src/site/markdown/release-guide.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/site/markdown/release-guide.md b/src/site/markdown/release-guide.md
index e979eb1d..238d31dd 100644
--- a/src/site/markdown/release-guide.md
+++ b/src/site/markdown/release-guide.md
@@ -162,7 +162,7 @@ without the `-RCx` suffix will be put once the vote succeeds, on the same
commit (which will therefore have two tags). Tagging and signing is done using
the following command, with `-RCn` replaced with the Release Candidate number:
- git tag X.Y-RCn -s -u xxxxxxxxxxxxxxxxxx -m "Release Candidate n for version X.Y."
+ git tag X.Y-RCn -s -u 9A928E5485FBC44A2A4F9C2E9128808ECB6C9DED -m "Release Candidate n for version X.Y."
The tag should be verified using command:
@@ -280,7 +280,7 @@ publish the release.
As the vote passed, a final signed tag must be added to the succeeding release
candidate, verified and pushed:
- git tag X.Y -s -u xxxxxxxxxxxxxxxxxx -m "Version X.Y."
+ git tag X.Y -s -u 9A928E5485FBC44A2A4F9C2E9128808ECB6C9DED -m "Version X.Y."
git tag -v X.Y
git push --tags
--
GitLab