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.5 was issued on 2024-09-19.  There are currently 13 
patches in the queue cut down this way:
    - 5 MEDIUM, first one merged on 2024-10-01
    - 8 MINOR, first one merged on 2024-10-01

Thus the computed ideal release date for 3.0.6 would be 2024-10-29, which is in 
three weeks or less.

    Last release 2.9.11 was issued on 2024-09-19.  There are currently 13 
patches in the queue cut down this way:
    - 5 MEDIUM, first one merged on 2024-10-01
    - 8 MINOR, first one merged on 2024-10-01

Thus the computed ideal release date for 2.9.12 would be 2024-10-29, which is 
in three weeks or less.

    Last release 2.8.11 was issued on 2024-09-19.  There are currently 6 
patches in the queue cut down this way:
    - 1 MAJOR, first one merged on 2024-10-01
    - 3 MEDIUM, first one merged on 2024-10-01
    - 2 MINOR, first one merged on 2024-10-01

Thus the computed ideal release date for 2.8.12 would be 2024-10-29, which is 
in three weeks or less.

The current list of patches in the queue is:
 - 2.8                       - MAJOR   : ocsp: Separate refcount per instance 
and per store
 - 2.9, 3.0                  - MEDIUM  : queue: always dequeue the backend when 
redistributing the last server
 - 2.8, 2.9, 3.0             - MEDIUM  : cli: Deadlock when setting frontend 
maxconn
 - 2.9                       - MEDIUM  : quic: handle retransmit for standalone 
FIN STREAM
 - 2.8                       - MEDIUM  : mux-pt: Never fully close the 
connection on shutdown
 - 3.0                       - MEDIUM  : cli: Be sure to catch immediate client 
abort
 - 2.8                       - MEDIUM  : ssl: Fix crash when calling "update 
ssl ocsp-response" when an update is ongoing
 - 2.9, 3.0                  - MEDIUM  : stream: make stream_shutdown() 
async-safe
 - 2.9, 3.0                  - MEDIUM  : mux-h1/mux-h2: Reject upgrades with 
payload on H2 side only
 - 2.9, 3.0                  - MINOR   : h1: do not forward h2c upgrade header 
token
 - 2.9, 3.0                  - MINOR   : mux-h1: Fix condition to set EOI on SE 
during zero-copy forwarding
 - 2.8, 2.9, 3.0             - MINOR   : cfgparse-global: fix allowed args 
number for setenv
 - 3.0                       - MINOR   : mux-quic: report glitches to session
 - 2.8, 2.9, 3.0             - MINOR   : server: make sure the HMAINT state is 
part of MAINT
 - 2.9                       - MINOR   : quic: prevent freeze after early QCS 
closure
 - 2.9, 3.0                  - MINOR   : h2: reject extended connect for h2c 
protocol
 - 2.9, 3.0                  - MINOR   : queue: make sure that maintenance 
redispatches server queue
 - 2.9, 3.0                  - MINOR   : http-ana: Disable fast-fwd for 
unfinished req waiting for upgrade

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