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.0.3 was issued on 2024-07-11.  There are currently 13 
patches in the queue cut down this way:
    - 1 MAJOR, first one merged on 2024-07-29
    - 6 MEDIUM, first one merged on 2024-07-29
    - 6 MINOR, first one merged on 2024-07-29

Thus the computed ideal release date for 3.0.4 would be 2024-08-12, which was 
two weeks ago.

    Last release 2.9.9 was issued on 2024-06-14.  There are currently 30 
patches in the queue cut down this way:
    - 1 MAJOR, first one merged on 2024-07-29
    - 14 MEDIUM, first one merged on 2024-07-02
    - 15 MINOR, first one merged on 2024-07-02

Thus the computed ideal release date for 2.9.10 would be 2024-07-30, which was 
four weeks ago.

    Last release 2.8.10 was issued on 2024-06-14.  There are currently 34 
patches in the queue cut down this way:
    - 12 MEDIUM, first one merged on 2024-07-03
    - 22 MINOR, first one merged on 2024-07-03

Thus the computed ideal release date for 2.8.11 would be 2024-08-28, which is 
in one week or less.

    Last release 2.6.18 was issued on 2024-06-18.  There are currently 20 
patches in the queue cut down this way:
    - 8 MEDIUM, first one merged on 2024-06-19
    - 12 MINOR, first one merged on 2024-07-03

Thus the computed ideal release date for 2.6.19 would be 2024-09-17, which is 
in three weeks or less.

The current list of patches in the queue is:
 - 2.9, 3.0                  - MAJOR   : mux-h2: force a hard error upon short 
read with pending error
 - 2.8, 2.9, 3.0             - MEDIUM  : ssl_sock: fix deadlock in 
ssl_sock_load_ocsp() on error path
 - 2.6, 2.8, 2.9             - MEDIUM  : h3: ensure the ":scheme" pseudo header 
is totally valid
 - 2.8, 2.9, 3.0             - MEDIUM  : debug/cli: fix "show threads" crashing 
with low thread counts
 - 2.9                       - MEDIUM  : proxy: fix email-alert invalid free
 - 2.6, 2.8, 2.9             - MEDIUM  : h3: ensure the ":method" pseudo header 
is totally valid
 - 2.8, 2.9                  - MEDIUM  : bwlim: Be sure to never set the 
analyze expiration date in past
 - 2.8, 2.9                  - MEDIUM  : quic: fix race-condition in 
quic_get_cid_tid()
 - 2.9                       - MEDIUM  : stick-table: Decrement the ref count 
inside lock to kill a session
 - 2.6                       - MEDIUM  : cli: fix cli_output_msg() regression
 - 3.0                       - MEDIUM  : quic: prevent crash on accept queue 
full
 - 2.6, 2.8, 2.9, 3.0            - MEDIUM  : queue: deal with a rare TOCTOU in 
assign_server_and_queue()
 - 2.6, 2.8, 2.9, 3.0            - MEDIUM  : init: fix fd_hard_limit default in 
compute_ideal_maxconn
 - 2.8, 2.9                  - MEDIUM  : quic: fix possible exit from 
qc_check_dcid() without unlocking
 - 2.6, 2.8, 2.9             - MEDIUM  : h1: Reject empty Transfer-encoding 
header
 - 2.6, 2.8, 2.9             - MEDIUM  : spoe: Be sure to create a SPOE applet 
if none on the current thread
 - 2.6, 2.8, 2.9, 3.0            - MEDIUM  : jwt: Clear SSL error queue on 
error when checking the signature
 - 2.6, 2.8, 2.9             - MINOR   : quic: fix BUG_ON() on Tx pkt alloc 
failure
 - 2.8                       - MINOR   : proxy: fix source interface and usesrc 
leaks on deinit()
 - 2.8                       - MINOR   : proxy: fix header_unique_id leak on 
deinit()
 - 2.8                       - MINOR   : proxy: fix dyncookie_key leak on 
deinit()
 - 2.8, 2.9, 3.0             - MINOR   : session: Eval L4/L5 rules defined in 
the default section
 - 2.6, 2.8, 2.9, 3.0            - MINOR   : server: Don't warn fallback IP is 
used during init-addr resolution
 - 2.6, 2.8, 2.9             - MINOR   : jwt: don't try to load files with HMAC 
algorithm
 - 2.6, 2.8, 2.9, 3.0            - MINOR   : quic: Lack of precision when 
computing K (cubic only cc)
 - 2.6, 2.8, 2.9             - MINOR   : mux-quic: fix crash on qcs SD alloc 
failure
 - 2.6, 2.8, 2.9             - MINOR   : jwt: fix variable initialisation
 - 2.6, 2.8, 2.9             - MINOR   : h1: Reject empty coding name as last 
transfer-encoding value
 - 3.0                       - MINOR   : quic: Non optimal first datagram.
 - 2.8, 2.9                  - MINOR   : h3: fix crash on STOP_SENDING receive 
after GOAWAY emission
 - 2.8, 2.9                  - MINOR   : quic: fix race condition in 
qc_check_dcid()
 - 2.6, 2.8, 2.9, 3.0            - MINOR   : cli: Atomically inc the global 
request counter between CLI commands
 - 2.8                       - MINOR   : proxy: fix log_tag leak on deinit()
 - 2.6, 2.8                  - MINOR   : quic: fix computed length of emitted 
STREAM frames
 - 2.6, 2.8, 2.9             - MINOR   : hlua: report proper context upon error 
in hlua_cli_io_handler_fct()
 - 2.8                       - MINOR   : proxy: fix check_{command,path} leak 
on deinit()
 - 2.8                       - MINOR   : proxy: fix server_id_hdr_name leak on 
deinit()
 - 2.8, 2.9                  - MINOR   : quic: fix race-condition on trace for 
CID retrieval
 - 2.6, 2.8, 2.9             - MINOR   : h1: Fail to parse empty transfer 
coding names
 - 2.6, 2.8, 2.9, 3.0            - MINOR   : stick-table: fix crash for 
src_inc_gpc() without stkcounter

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