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 1.8.23 was issued on 2019/11/25.  There are currently 17 patches 
in the queue cut down this way:
    - 1 MAJOR, first one merged on 2019/12/10
    - 5 MEDIUM, first one merged on 2019/12/05
    - 11 MINOR, first one merged on 2019/12/05

Thus the computed ideal release date for 1.8.24 would be 2019/12/24, which was 
one week ago.

The current list of patches in the queue is:
    - MAJOR   : dns: add minimalist error processing on the Rx path
    - MEDIUM  : ssl: Don't set the max early data we can receive too early.
    - MEDIUM  : kqueue: Make sure we report read events even when no data.
    - MEDIUM  : proto_udp/threads: recv() and send() must not be exclusive.
    - MEDIUM  : listener/threads: fix a remaining race in the listener's 
    - MEDIUM  : listener/thread: fix a race when pausing a listener
    - MINOR   : listener: fix off-by-one in state name check
    - MINOR   : server: make "agent-addr" work on default-server line
    - MINOR   : listener: do not immediately resume on transient error
    - MINOR   : listener: also clear the error flag on a paused listener
    - MINOR   : proxy: make soft_stop() also close FDs in LI_PAUSED state
    - MINOR   : listener/threads: always use atomic ops to clear the FD events
    - MINOR   : sample: always check converters' arguments
    - MINOR   : sample: fix the closing bracket and LF in the debug converter
    - MINOR   : ssl: certificate choice can be unexpected with openssl >= 1.1.1
    - MINOR   : mworker: properly pass SIGTTOU/SIGTTIN to workers
    - MINOR   : log: fix minor resource leaks on logformat error path

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