romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-04-14 21:41:41 +03:00
Code Issues Projects Releases Packages Wiki Activity

RELEASE-PROCEDURE.md: release candidate git tagging explained

Browse source 
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
This commit is contained in:
Daniel Stenberg 2025-04-24 22:57:51 +02:00
parent 991c30d0d6
commit de8622b858
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
1 changed files with 6 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/RELEASE-PROCEDURE.md
View file

@ -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.