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.2.1 was issued on 2025-06-11.  There are currently 2 patches 
in the queue cut down this way:
    - 2 MINOR, first one merged on 2025-06-13

Thus the computed ideal release date for 3.2.2 would be 2025-07-11, which is in 
four weeks or less.

    Last release 2.8.15 was issued on 2025-04-22.  There are currently 21 
patches in the queue cut down this way:
    - 1 MAJOR, first one merged on 2025-05-27
    - 20 MINOR, first one merged on 2025-05-27

Thus the computed ideal release date for 2.8.16 would be 2025-07-08, which is 
in three weeks or less.

The current list of patches in the queue is:
 - 2.8                       - MAJOR   : listeners: transfer connection 
accounting when switching listeners
 - 2.8                       - MINOR   : limits: compute_ideal_maxconn: don't 
cap remain if fd_hard_limit=0
 - 2.8                       - MINOR   : h3: Set HTX flags corresponding to the 
scheme found in the request
 - 2.8                       - MINOR   : quic: use proper error code on invalid 
received TP value
 - 2.8                       - MINOR   : proxy: only use 
proxy_inc_fe_cum_sess_ver_ctr() with frontends
 - 2.8                       - MINOR   : threads: fix soft-stop without 
multithreading support
 - 2.8                       - MINOR   : quic: reject invalid max_udp_payload 
size
 - 2.8                       - MINOR   : quic: use proper error code on missing 
CID in TPs
 - 2.8                       - MINOR   : dns: add tempo between 2 connection 
attempts for dns servers
 - 3.2                       - MINOR   : http-ana: Properly handle keep-query 
redirect option if no QS
 - 2.8                       - MINOR   : quic: reject retry_source_cid TP on 
server side
 - 2.8                       - MINOR   : mux-h1: Don't pretend connection was 
released for TCP>H1>H2 upgrade
 - 2.8                       - MINOR   : cli: Issue an error when too many args 
are passed for a command
 - 2.8                       - MINOR   : sink: detect and warn when using 
"send-proxy" options with ring servers
 - 2.8                       - MINOR   : quic: use proper error code on invalid 
server TP
 - 2.8                       - MINOR   : mux-h2: Reset streams with NO_ERROR 
code if full response was already sent
 - 2.8                       - MINOR   : quic: fix TP reject on invalid 
max-ack-delay
 - 2.8                       - MINOR   : cli: fix too many args detection for 
commands
 - 2.8                       - MINOR   : h3: don't insert more than one Host 
header
 - 2.8                       - MINOR   : hlua: Fix Channel:data() and 
Channel:line() to respect documentation
 - 2.8                       - MINOR   : dns: prevent ds accumulation within dss
 - 3.2                       - MINOR   : config/server: reject QUIC addresses
 - 2.8                       - MINOR   : mux-h1: Fix trace message in 
h1_detroy() to not relay on connection

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


Reply via email to