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.9.9 was issued on 2019/07/23.  There are currently 15 patches in 
the queue cut down this way:
    - 2 MAJOR, first one merged on 2019/07/30
    - 7 MEDIUM, first one merged on 2019/07/26
    - 6 MINOR, first one merged on 2019/07/26

Thus the computed ideal release date for 1.9.10 would be 2019/08/13, which is 
in two weeks or less.

The current list of patches in the queue is:
    - MAJOR   : queue/threads: avoid an AB/BA locking issue in 
    - MAJOR   : http/sample: use a static buffer for raw -> htx conversion
    - MEDIUM  : streams: Don't switch the SI to SI_ST_DIS if we have data to 
    - MEDIUM  : lb-chash: Fix the realloc() when the number of nodes is 
    - MEDIUM  : lb-chash: Ensure the tree integrity when server weight is 
    - MEDIUM  : protocols: add a global lock for the init/deinit stuff
    - MEDIUM  : mux-h2: split the stream's and connection's window sizes
    - MEDIUM  : mux-h2: unbreak receipt of large DATA frames
    - MEDIUM  : hlua: Check the calling direction in lua functions of the HTTP 
    - MINOR   : hlua: Only execute functions of HTTP class if the txn is HTTP 
    - MINOR   : stream-int: also update analysers timeouts on activity
    - MINOR   : lua: Set right direction and flags on new HTTP objects
    - MINOR   : hlua/htx: Reset channels analyzers when txn:done() is called
    - MINOR   : log: make sure writev() is not interrupted on a file output
    - MINOR   : proxy: always lock stop_proxy()

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