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.3.9 was issued on 2026-05-06. There are currently 7 patches
in the queue cut down this way:
- 4 MEDIUM, first one merged on 2026-05-07
- 3 MINOR, first one merged on 2026-05-07
Thus the computed ideal release date for 3.3.10 would be 2026-06-04, which is
in four weeks or less.
Last release 3.2.18 was issued on 2026-05-06. There are currently 5
patches in the queue cut down this way:
- 4 MEDIUM, first one merged on 2026-05-07
- 1 MINOR, first one merged on 2026-05-07
Thus the computed ideal release date for 3.2.19 would be 2026-06-04, which is
in four weeks or less.
Last release 3.0.22 was issued on 2026-05-06. There are currently 5
patches in the queue cut down this way:
- 4 MEDIUM, first one merged on 2026-05-07
- 1 MINOR, first one merged on 2026-05-07
Thus the computed ideal release date for 3.0.23 would be 2026-07-02, which is
in eight weeks or less.
Last release 2.8.23 was issued on 2026-05-06. There are currently 6
patches in the queue cut down this way:
- 5 MEDIUM, first one merged on 2026-05-06
- 1 MINOR, first one merged on 2026-05-07
Thus the computed ideal release date for 2.8.24 would be 2026-07-30, which is
in twelve weeks or less.
The current list of patches in the queue is:
- 2.8, 3.0, 3.2, 3.3 - MEDIUM : stick-table: properly check
permissions on CLI's set/clear cmd
- 2.8 - MEDIUM : h1: Enforce the authority validation
during H1 request parsing
- 2.8, 3.0, 3.2, 3.3 - MEDIUM : mux-h2: fix the detection of the
ext connect support
- 2.8, 3.0, 3.2, 3.3 - MEDIUM : mux-h2: Properly consume padding
for DATA frames
- 2.8, 3.0, 3.2, 3.3 - MEDIUM : cli: fix master CLI connection
slot leak on client disconnect"
- 3.3 - MINOR : mux_quic: fix max stream ID reuse
estimation
- 3.3 - MINOR : ssl: Use the sequence number with kTLS
and TLS 1.2
- 2.8, 3.0, 3.2, 3.3 - MINOR : mux-h2: condition the processing
of 8441 extension to global setting"
--
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.
