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 2.8.14 was issued on 2025-01-29.  There are currently 5 
patches in the queue cut down this way:
    - 3 MEDIUM, first one merged on 2025-02-11
    - 2 MINOR, first one merged on 2025-02-19

Thus the computed ideal release date for 2.8.15 would be 2025-04-12, which is 
in two weeks or less.

    Last release 2.6.21 was issued on 2025-01-29.  There are currently 9 
patches in the queue cut down this way:
    - 3 MEDIUM, first one merged on 2025-02-11
    - 6 MINOR, first one merged on 2025-02-19

Thus the computed ideal release date for 2.6.22 would be 2025-05-12, which is 
in six weeks or less.

The current list of patches in the queue is:
 - 2.8                       - MEDIUM  : clock: make sure now_ms cannot be 
TICK_ETERNITY
 - 2.6, 2.8                  - MEDIUM  : spoe: Don't wakeup idle applets in 
loop during stopping
 - 2.6                       - MEDIUM  : mux-h1/mux-h2: Reject upgrades with 
payload on H2 side only
 - 2.6, 2.8                  - MEDIUM  : ssl: chosing correct certificate using 
RSA-PSS with TLSv1.3
 - 2.6, 2.8                  - MINOR   : spoe: Check the shared waiting queue 
to shut applets during stopping
 - 2.6                       - MINOR   : h1: do not forward h2c upgrade header 
token
 - 2.6                       - MINOR   : ssl_sock: fix xprt_set_used() to 
properly clear the TASK_F_USR1 bit
 - 2.6, 2.8                  - MINOR   : spoe: Allow applet creation when 
closing the last one during stopping
 - 2.6                       - MINOR   : http-ana: Disable fast-fwd for 
unfinished req waiting for upgrade
 - 2.6                       - MINOR   : h2: reject extended connect for h2c 
protocol

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