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 1.9.8 was issued on 2019/05/13.  There are currently 14 patches in 
the queue cut down this way:
    - 1 MAJOR, first one merged on 2019/05/27
    - 8 MEDIUM, first one merged on 2019/05/21
    - 5 MINOR, first one merged on 2019/05/16

Thus the computed ideal release date for 1.9.9 would be 2019/06/10, which is in 
one week or less.

The current list of patches in the queue is:
    - MAJOR   : lb/threads: make sure the avoided server is not full on second 
pass
    - MEDIUM  : spoe: Don't use the SPOE applet after releasing it
    - MEDIUM  : threads: Fix build for 32bits arch with dwcas.
    - MEDIUM  : dns: make the port numbers unsigned
    - MEDIUM  : proto-htx: Not forward too much data when 1xx reponses are 
handled
    - MEDIUM  : streams: Don't switch from SI_ST_CON to SI_ST_DIS on read0.
    - MEDIUM  : queue: fix the tree walk in pendconn_redistribute.
    - MEDIUM  : WURFL: segfault in wurfl-get() with missing info.
    - MEDIUM  : threads: fix double-word CAS on non-optimized 32-bit platforms
    - MINOR   : ssl_sock: Fix memory leak when disabling compression
    - MINOR   : mux-h2: Count EOM in bytes sent when a HEADERS frame is 
formatted
    - MINOR   : http_fetch: Rely on the smp direction for "cookie()" and "hdr()"
    - MINOR   : mux-h1: Report EOI instead EOS on parsing error or H2 upgrade
    - MINOR   : htx: Remove a forgotten while loop in htx_defrag()

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