Artifactspublic-v0

curl

master
ply4 git calls28 ms289 KiB3 cachedprotocol v2
134 lines4.3 KiBRaw

curl release procedure - how to do a release

in the source code repo

  • edit RELEASE-NOTES to be accurate

  • update docs/THANKS

  • update the "past releases" section in docs/VERSIONS.md

  • make sure all relevant changes are committed on the master branch

  • tag the git repo in this style: git tag -a curl-7_34_0. -a annotates the tag and we use underscores instead of dots in the version number. Make sure the tag is GPG signed (using -s).

  • run ./scripts/dmaketgz 7.34.0 to build the release tarballs.

  • push the git commits and the new tag

  • GPG sign the 4 tarballs as maketgz suggests

  • upload the 8 resulting files to the primary download directory

in the curl-www repo

  • edit Makefile (version number and date),

  • edit _changes.html (insert changes+bugfixes from RELEASE-NOTES)

  • commit all local changes

  • tag the repo with the same name as used for the source repo.

  • make sure all relevant changes are committed and pushed on the master branch

    (the website then updates its contents automatically)

on GitHub

  • edit the newly made release tag so that it is listed as the latest release

inform

  • send an email to curl-users, curl-announce and curl-library. Insert the RELEASE-NOTES into the mail.

  • if there are any advisories associated with the release, send each markdown file to the above lists as well as to oss-security@lists.openwall.com (unless the problem is unique to the non-open operating systems)

celebrate

  • suitable beverage intake is encouraged for the festivities

curl release scheduling

Release Cycle

We normally do releases every 8 weeks on Wednesdays. If important problems arise, we can insert releases outside the schedule or we can move the release date.

Each 8 week (56 days) release cycle is divided into three distinct periods:

  • During the first 10 calendar days after a release, we are in "cool down". We do not merge features but only bug-fixes. If a regression is reported, we might do a follow-up patch release.

  • During the following 3 weeks (21 days) there is a feature window: we allow new features and changes to curl and libcurl. If we accept any such changes, we bump the minor number used for the next release.

  • During the next 25 days we are in feature freeze. We do not merge any features or changes, and we only focus on fixing bugs and polishing things to make the pending release a solid one.

If a future release date happens to end up on a "bad date", like in the middle 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. Tagged like rc-7_34_0-1.

  • Release candidate two (rc2) ships nine days later, sixteen days before the release. On a Monday. Tagged like rc-7_34_0-2.

  • Release candidate three (rc3) ships nine days later, seven days before 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 candidates 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.

Critical problems

We can break the release cycle and do a patch release at any point if a critical enough problem is reported. There is no exact definition of how to assess such criticality, but if an issue is highly disturbing or has a security impact on a large enough share of the user population it might qualify.

If you think an issue qualifies, bring it to the curl-library mailing list and push for it.

Coming dates

Based on the description above, here are some planned future release dates:

  • October 14, 2026
  • December 9, 2026
  • February 3, 2027
  • March 31, 2027
  • May 26, 2027
  • July 21, 2027
  • September 15, 2027
1<!--
2Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
4SPDX-License-Identifier: curl
5-->
7# curl release procedure - how to do a release
9## in the source code repo
11- edit `RELEASE-NOTES` to be accurate
13- update `docs/THANKS`
15- update the "past releases" section in `docs/VERSIONS.md`
17- make sure all relevant changes are committed on the master branch
19- tag the git repo in this style: `git tag -a curl-7_34_0`. -a annotates the
20 tag and we use underscores instead of dots in the version number. Make sure
21 the tag is GPG signed (using -s).
23- run `./scripts/dmaketgz 7.34.0` to build the release tarballs.
25- push the git commits and the new tag
27- GPG sign the 4 tarballs as `maketgz` suggests
29- upload the 8 resulting files to the primary download directory
31## in the curl-www repo
33- edit `Makefile` (version number and date),
35- edit `_changes.html` (insert changes+bugfixes from RELEASE-NOTES)
37- commit all local changes
39- tag the repo with the same name as used for the source repo.
41- make sure all relevant changes are committed and pushed on the master branch
43 (the website then updates its contents automatically)
45## on GitHub
47- edit the newly made release tag so that it is listed as the latest release
49## inform
51- send an email to curl-users, curl-announce and curl-library. Insert the
52 RELEASE-NOTES into the mail.
54- if there are any advisories associated with the release, send each markdown
55 file to the above lists as well as to `oss-security@lists.openwall.com`
56 (unless the problem is unique to the non-open operating systems)
58## celebrate
60- suitable beverage intake is encouraged for the festivities
62# curl release scheduling
64## Release Cycle
66We normally do releases every 8 weeks on Wednesdays. If important problems
67arise, we can insert releases outside the schedule or we can move the release
68date.
70Each 8 week (56 days) release cycle is divided into three distinct periods:
72- During the first 10 calendar days after a release, we are in "cool down". We
73 do not merge features but only bug-fixes. If a regression is reported, we
74 might do a follow-up patch release.
76- During the following 3 weeks (21 days) there is a feature window: we allow
77 new features and changes to curl and libcurl. If we accept any such changes,
78 we bump the minor number used for the next release.
80- During the next 25 days we are in feature freeze. We do not merge any
81 features or changes, and we only focus on fixing bugs and polishing things
82 to make the pending release a solid one.
84If a future release date happens to end up on a "bad date", like in the middle
85of common public holidays or when the lead release manager is unavailable, the
86release date can be moved forwards or backwards a full week. This is then
87advertised well in advance.
89# Release Candidates
91We ship release candidate tarballs on three occasions in preparation for the
92pending release:
94- Release candidate one (**rc1**) ships the same Saturday the feature freeze
95 starts. Twenty-five days before the release. Tagged like `rc-7_34_0-1`.
97- Release candidate two (**rc2**) ships nine days later, sixteen days before
98 the release. On a Monday. Tagged like `rc-7_34_0-2`.
100- Release candidate three (**rc3**) ships nine days later, seven days before
101 the release. On a Wednesday. Tagged like `rc-7_34_0-3`.
103Release candidate tarballs are ephemeral and each such tarball is only kept
104around for a few weeks. They are provided on their dedicated webpage at:
105https://curl.se/rc/
107The git tags for release candidates are temporary and remain set only for a
108limited period of time.
110**Do not use release candidates in production**. They are work in progress.
111Use them for testing and verification only. Use actual releases in production.
113# Critical problems
115We can break the release cycle and do a patch release at any point if a
116critical enough problem is reported. There is no exact definition of how to
117assess such criticality, but if an issue is highly disturbing or has a
118security impact on a large enough share of the user population it might
119qualify.
121If you think an issue qualifies, bring it to the curl-library mailing list and
122push for it.
124# Coming dates
126Based on the description above, here are some planned future release dates:
128- October 14, 2026
129- December 9, 2026
130- February 3, 2027
131- March 31, 2027
132- May 26, 2027
133- July 21, 2027
134- September 15, 2027
Diagnostics4 git calls · 28 ms
CallStatusSizeTime028 ms
discover200152 B3 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=3
git.response.bytes=152
git.server.agent=gitty/1.0
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch object-format
git.server.fetch=shallow filter sideband-all
git.protocol.version=2
git.pkt.frames=8
git.pkt.data=6
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=152
git.pkt.payload.max=34
ls-refs200149 B · hit3 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=3
git.response.bytes=149
git.response.cache=HIT
git.response.duration_ms=3
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=149
git.pkt.payload.max=78
git.ls_refs.count=2
git.ls_refs.head=refs/heads/master
fetchblob:none · deepen 10200287 KiB · hit3 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=22
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=3
git.fetch.filter=blob:none
git.fetch.filter.requested=tree:0
git.fetch.filter.fallback=blob:none
git.fetch.filter.learned=false
git.fetch.wants=31c911efe5652725e930f4d2e60c9060e5f6646d
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=10
git.pkt.data=8
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=293470
git.pkt.payload.max=65516
git.sideband.band1.bytes=293354
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=87
git.pack.bytes=293354
git.pack.ofs_delta=0
git.pack.ref_delta=1
git.pack.chain.max=1
git.pack.trailer=6a646bcda6740bab42e321b51998b52ea15146c0
git.pack.full=86
Open pack map
fetch2002.1 KiB · hit22 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=2118
git.response.cache=HIT
git.response.duration_ms=22
git.fetch.wants=38ee29d3d802d8ccdb7f8829cd0c177fd483f7bb
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=2118
git.pkt.payload.max=2097
git.sideband.band1.bytes=2096
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://5ad2236b39de4c8bd8f6270ea63f3ea9.artifacts.cloudflare.net/git/public-v0/curl.git
Ref
refs/heads/master
Commit
31c911efe5652725e930f4d2e60c9060e5f6646d
cf-ray
a5e1723d59ac6102
Request
5b591d1e…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format