From 124c2bed2add15bd30c7bf2463468f010a08bbc2 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Sat, 8 Mar 2025 10:38:49 +0100 Subject: [PATCH] RELEASE-PROCEDURE.md: explain release candidates Closes #16622 --- docs/RELEASE-PROCEDURE.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/docs/RELEASE-PROCEDURE.md b/docs/RELEASE-PROCEDURE.md index 225a46f421..826f7462fe 100644 --- a/docs/RELEASE-PROCEDURE.md +++ b/docs/RELEASE-PROCEDURE.md @@ -94,6 +94,28 @@ of common public holidays or when the lead release manager is unavailable, the release date can be moved forwards or backwards a full week. This is then advertised well in advance. +Release Candidates +------------------ + +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. + +- Release candidate two (**rc2**) ships nine days later, sixteen days before + the release. On a Monday. + +- Release candidate tree (**rc3**) ships nine days later, seven days before + the release. On a Wednesday. + +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/ + +**Do not use release candidates in production**. They are work in progress. +Use them for testing and verification only. Use actual releases in production. + Critical problems ----------------- -- 2.47.3