Hi,
This is a friendly bot that watches fixes pending for the next haproxy-stable
release! One such e-mail is sent periodically once patches are waiting in the
last maintenance branch, and an ideal release date is computed based on the
severity of these fixes and their merge date. Responses to this mail must be
sent to the mailing list.
Last release 3.1.5 was issued on 2025-02-20. There are currently 13
patches in the queue cut down this way:
- 5 MEDIUM, first one merged on 2025-02-21
- 8 MINOR, first one merged on 2025-02-21
Thus the computed ideal release date for 3.1.6 would be 2025-03-21, which is in
two weeks or less.
Last release 3.0.8 was issued on 2025-01-29. There are currently 6 patches
in the queue cut down this way:
- 3 MEDIUM, first one merged on 2025-02-11
- 3 MINOR, first one merged on 2025-02-19
Thus the computed ideal release date for 3.0.9 would be 2025-03-13, which is in
one week or less.
Last release 2.9.14 was issued on 2025-01-29. There are currently 4
patches in the queue cut down this way:
- 2 MEDIUM, first one merged on 2025-02-11
- 2 MINOR, first one merged on 2025-02-19
Thus the computed ideal release date for 2.9.15 would be 2025-04-12, which is
in five weeks or less.
Last release 2.8.14 was issued on 2025-01-29. There are currently 5
patches in the queue cut down this way:
- 3 MEDIUM, first one merged on 2025-02-11
- 2 MINOR, first one merged on 2025-02-19
Thus the computed ideal release date for 2.8.15 would be 2025-04-12, which is
in five weeks or less.
Last release 2.6.21 was issued on 2025-01-29. There are currently 9
patches in the queue cut down this way:
- 3 MEDIUM, first one merged on 2025-02-11
- 6 MINOR, first one merged on 2025-02-19
Thus the computed ideal release date for 2.6.22 would be 2025-05-12, which is
in nine weeks or less.
The current list of patches in the queue is:
- 2.6 - MEDIUM : mux-h1/mux-h2: Reject upgrades with
payload on H2 side only
- 3.1 - MEDIUM : server: properly initialize PROXY v2
TLVs
- 3.1 - MEDIUM : uxst: fix outgoing abns address family
in connect()
- 2.8 - MEDIUM : clock: make sure now_ms cannot be
TICK_ETERNITY
- 3.1 - MEDIUM : stream: use non-blocking freq_ctr
calls from the stream dumper
- 3.1 - MEDIUM : mux-fcgi: Try to fully fill demux
buffer on receive if not empty
- 3.0 - MEDIUM : mux-quic: do not attach on already
closed stream
- 3.1 - MEDIUM : stream: never allocate connection
addresses from signal handler
- 2.6, 2.8, 2.9, 3.0 - MEDIUM : ssl: chosing correct certificate
using RSA-PSS with TLSv1.3
- 2.6, 2.8, 2.9, 3.0 - MEDIUM : spoe: Don't wakeup idle applets in
loop during stopping
- 3.1 - MINOR : stream: do not call co_data() from
__strm_dump_to_buffer()
- 3.1 - MINOR : h3: do not report transfer as aborted
on preemptive response
- 3.1 - MINOR : mux-h1: always make sure h1s->sd
exists in h1_dump_h1s_info()
- 2.6 - MINOR : h2: reject extended connect for h2c
protocol
- 2.6 - MINOR : h1: do not forward h2c upgrade header
token
- 2.6, 2.8, 2.9, 3.0 - MINOR : spoe: Check the shared waiting
queue to shut applets during stopping
- 2.6 - MINOR : http-ana: Disable fast-fwd for
unfinished req waiting for upgrade
- 3.1 - MINOR : sink: add tempo between 2 connection
attempts for sft servers
- 3.1 - MINOR : h2: always trim leading and trailing
LWS in header values
- 2.6 - MINOR : ssl_sock: fix xprt_set_used() to
properly clear the TASK_F_USR1 bit
- 3.1 - MINOR : log: fix outgoing abns address family
- 3.1 - MINOR : cfgparse: fix NULL ptr dereference in
cfg_parse_peers
- 3.1 - MINOR : server: fix the "server-template"
prefix memory leak
- 3.0 - MINOR : mux-quic: handle closure of uni-stream
- 2.6, 2.8, 2.9, 3.0 - MINOR : spoe: Allow applet creation when
closing the last one during stopping
--
The haproxy stable-bot is freely provided by HAProxy Technologies to help
improve the quality of each HAProxy release. If you have any issue with these
emails or if you want to suggest some improvements, please post them on the
list so that the solutions suiting the most users can be found.
