From de8622b858e59e5460faf052ded9f65853c86efd Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Thu, 24 Apr 2025 22:57:51 +0200 Subject: [PATCH] RELEASE-PROCEDURE.md: release candidate git tagging explained To help anyone wanting to build/reproduce release candidates, this is the set git tag naming scheme to use. Similar to, but different, than the "normal" release tags to not be possible to mixup. Closes #17177 --- docs/RELEASE-PROCEDURE.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/RELEASE-PROCEDURE.md b/docs/RELEASE-PROCEDURE.md index 826f7462fe..5cf08162f9 100644 --- a/docs/RELEASE-PROCEDURE.md +++ b/docs/RELEASE-PROCEDURE.md @@ -101,18 +101,21 @@ We ship release candidate tarballs on three occasions in preparation for the pending release: - Release candidate one (**rc1**) ships the same Saturday the feature freeze - starts. Twenty-five days before the release. + starts. Twenty-five days before the release. Tagged like `rc-7_34_0-1`. - Release candidate two (**rc2**) ships nine days later, sixteen days before - the release. On a Monday. + the release. On a Monday. Tagged like `rc-7_34_0-2`. - Release candidate tree (**rc3**) ships nine days later, seven days before - the release. On a Wednesday. + the release. On a Wednesday. Tagged like `rc-7_34_0-3`. Release candidate tarballs are ephemeral and each such tarball is only kept around for a few weeks. They are provided on their dedicated webpage at: https://curl.se/rc/ +The git tags for release candidate are temporary and remain set only for a +limited period of time. + **Do not use release candidates in production**. They are work in progress. Use them for testing and verification only. Use actual releases in production. -- 2.47.3