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.4 was issued on 2026-02-19.  There are currently 1 patches 
in the queue cut down this way:
    - 1 MEDIUM, first one merged on 2026-02-26

Thus the computed ideal release date for 3.3.5 would be 2026-03-28, which is in 
three weeks or less.

    Last release 3.2.13 was issued on 2026-02-19.  There are currently 1 
patches in the queue cut down this way:
    - 1 MEDIUM, first one merged on 2026-02-26

Thus the computed ideal release date for 3.2.14 would be 2026-03-28, which is 
in three weeks or less.

    Last release 3.1.15 was issued on 2026-02-19.  There are currently 1 
patches in the queue cut down this way:
    - 1 MEDIUM, first one merged on 2026-02-26

Thus the computed ideal release date for 3.1.16 would be 2026-04-27, which is 
in seven weeks or less.

    Last release 3.0.17 was issued on 2026-02-19.  There are currently 1 
patches in the queue cut down this way:
    - 1 MEDIUM, first one merged on 2026-02-26

Thus the computed ideal release date for 3.0.18 would be 2026-04-27, which is 
in seven weeks or less.

    Last release 2.8.18 was issued on 2025-12-25.  There are currently 20 
patches in the queue cut down this way:
    - 9 MEDIUM, first one merged on 2026-01-07
    - 11 MINOR, first one merged on 2026-01-09

Thus the computed ideal release date for 2.8.19 would be 2026-04-03, which is 
in four weeks or less.

The current list of patches in the queue is:
 - 2.8                       - MEDIUM  : ssl: fix error path on 
generate-certificates
 - 2.8                       - MEDIUM  : config: Use the mux protocol ALPN by 
default for listeners if forced
 - 2.8                       - MEDIUM  : quic: fix ACK ECN frame parsing
 - 2.8                       - MEDIUM  : hlua: fix invalid lua_pcall() usage in 
hlua_traceback()
 - 3.0, 3.1, 3.2, 3.3            - MEDIUM  : mux-h2: make sure to always report 
pending errors to the stream
 - 2.8                       - MEDIUM  : http-ana: Properly detect client abort 
when forwarding response (v2)
 - 2.8                       - MEDIUM  : debug: only dump Lua state when 
panicking
 - 2.8                       - MEDIUM  : mux-h2: synchronize all conditions to 
create a new backend stream
 - 2.8                       - MEDIUM  : stconn: Don't report abort from SC if 
read0 was already received
 - 2.8                       - MEDIUM  : ssl: fix generate-certificates option 
when SNI greater than 64bytes
 - 2.8                       - MINOR   : hlua: consume error object if ignored 
after a failing lua_pcall()
 - 2.8                       - MINOR   : proxy: free persist_rules
 - 2.8                       - MINOR   : backend: inspect request not response 
buffer to check for TFO
 - 2.8                       - MINOR   : cfgparse: wrong section name upon error
 - 2.8                       - MINOR   : backend: fix the conn_retries check 
for TFO
 - 2.8                       - MINOR   : http_act: fix deinit performed on 
uninitialized lf_expr in release_http_map()
 - 2.8                       - MINOR   : sock-inet: ignore conntrack for 
transparent sockets on Linux
 - 2.8                       - MINOR   : cli/stick-tables: argument to "show 
table" is optional
 - 2.8                       - MINOR   : ssl: fix error message of 
tune.ssl.certificate-compression
 - 2.8                       - MINOR   : promex: Detach promex from the server 
on error dump its metrics dump
 - 2.8                       - MINOR   : cfgparse: fix "default" prefix parsing

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