Artifactspublic-v0

curl

master
ply4 git calls33 ms288 KiB3 cachedprotocol v2
73 lines2.9 KiBRaw

How to determine if an early patch release is warranted

In the curl project we do releases every 8 weeks. Unless we break the cycle and do an early patch release.

We do frequent releases partly to always have the next release "not too far away".

Bugfix

During the release cycle, and especially in the beginning of a new cycle (the so-called "cool down" period), there are times when a bug is reported and after it has been subsequently fixed correctly, the question might be asked: is this bug and associated fix important enough for an early patch release?

The question can only be properly asked when a fix has been created and landed in the git master branch.

Early release

An early patch release means that we ship a new, complete and full release called major.minor.patch where the patch part is increased by one since the previous release. A curl release is a curl release. There is no small or big and we never ship stand-alone separate patches. There is only "release".

Questions to ask

  • Is there a security advisory rated high or critical?
  • Is there a data corruption bug?
  • Did the bug cause an API/ABI breakage?
  • Does the problem annoy a significant share of the user population?

If the answer is yes to one or more of the above, an early release might be warranted.

More questions to ask ourselves when doing the assessment if the answers to the three ones above are all 'no'.

  • Does the bug cause curl to prematurely terminate?
  • How common is the affected buggy option/feature/protocol/platform to get used?
  • How large is the estimated impacted user base?
  • Does the bug block something crucial for applications or other adoption of curl "out there" ?
  • Does the bug cause problems for curl developers or others on "the curl team" ?
  • Is the bug limited to the curl tool only? That might have a smaller impact than a bug also present in libcurl.
  • Is there a (decent) workaround?
  • Is it a regression? Is the bug introduced in this release?
  • Can the bug be fixed "easily" by applying a patch?
  • Does the bug break the build? Most users do not build curl themselves.
  • How long is it until the already scheduled next release?
  • Can affected users safely revert to a former release until the next scheduled release?
  • Is it a performance regression with no functionality side-effects? If so it has to be substantial.

If an early release is deemed necessary

Unless done for security or similarly important reasons, an early release should not be done within a week of the previous release.

This, to enable us to collect and bundle more fixes into the same release to make the release more worthwhile for everyone and to allow more time for fixes to settle and things to get tested. Getting a release in shape and done in style is work that should not be rushed.

1<!--
2Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
4SPDX-License-Identifier: curl
5-->
7# How to determine if an early patch release is warranted
9In the curl project we do releases every 8 weeks. Unless we break the cycle
10and do an early patch release.
12We do frequent releases partly to always have the next release "not too far
13away".
15## Bugfix
17During the release cycle, and especially in the beginning of a new cycle (the
18so-called "cool down" period), there are times when a bug is reported and
19after it has been subsequently fixed correctly, the question might be asked:
20is this bug and associated fix important enough for an early patch release?
22The question can only be properly asked when a fix has been created and landed
23in the git master branch.
25## Early release
27An early patch release means that we ship a new, complete and full release
28called `major.minor.patch` where the `patch` part is increased by one since
29the previous release. A curl release is a curl release. There is no small or
30big and we never ship stand-alone separate patches. There is only "release".
32## Questions to ask
34- Is there a security advisory rated high or critical?
35- Is there a data corruption bug?
36- Did the bug cause an API/ABI breakage?
37- Does the problem annoy a significant share of the user population?
39If the answer is yes to one or more of the above, an early release might be
40warranted.
42More questions to ask ourselves when doing the assessment if the answers to
43the three ones above are all 'no'.
45- Does the bug cause curl to prematurely terminate?
46- How common is the affected buggy option/feature/protocol/platform to get
47 used?
48- How large is the estimated impacted user base?
49- Does the bug block something crucial for applications or other adoption of
50 curl "out there" ?
51- Does the bug cause problems for curl developers or others on "the curl
52 team" ?
53- Is the bug limited to the curl tool only? That might have a smaller impact
54 than a bug also present in libcurl.
55- Is there a (decent) workaround?
56- Is it a regression? Is the bug introduced in this release?
57- Can the bug be fixed "easily" by applying a patch?
58- Does the bug break the build? Most users do not build curl themselves.
59- How long is it until the already scheduled next release?
60- Can affected users safely revert to a former release until the next
61 scheduled release?
62- Is it a performance regression with no functionality side-effects? If so it
63 has to be substantial.
65## If an early release is deemed necessary
67Unless done for security or similarly important reasons, an early release
68should not be done within a week of the previous release.
70This, to enable us to collect and bundle more fixes into the same release to
71make the release more worthwhile for everyone and to allow more time for fixes
72to settle and things to get tested. Getting a release in shape and done in
73style is work that should not be rushed.
Diagnostics4 git calls · 33 ms
CallStatusSizeTime033 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=2
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 · hit2 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=28
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=2
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
fetch2001.4 KiB · hit28 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=1467
git.response.cache=HIT
git.response.duration_ms=28
git.fetch.wants=833a785ce064c0509f28f9fc1f76ac0deac9b551
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=1467
git.pkt.payload.max=1446
git.sideband.band1.bytes=1445
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
a5e352549f03224d
Request
711c5cd0…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format