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.0.2 was issued on 2019/07/16. There are currently 14 patches in the queue cut down this way: - 3 MEDIUM, first one merged on 2019/07/19 - 11 MINOR, first one merged on 2019/07/19 Thus the computed ideal release date for 2.0.3 would be 2019/08/16, which is in four weeks or less. The current list of patches in the queue is: - MEDIUM : http/htx: unbreak option http_proxy - MEDIUM : checks: Don't attempt to receive data if we already subscribed. - MEDIUM : mux-h1: Trim excess server data at the end of a transaction - MINOR : checks: do not exit tcp-checks from the middle of the loop - MINOR : session: Emit an HTTP error if accept fails only for H1 connection - MINOR : cache/htx: Make maxage calculation HTX aware - MINOR : http_htx: Initialize HTX error messages for TCP proxies - MINOR : debug: Remove flags CO_FL_SOCK_WR_ENA/CO_FL_SOCK_RD_ENA - MINOR : http_fetch: Fix http_auth/http_auth_group when called from TCP rules - MINOR : mux-h1: Close server connection if input data remains in h1_detach() - MINOR : session: Send a default HTTP error if accept fails for a H1 socket - MINOR : hlua: Make the function txn:done() HTX aware - MINOR : backend: do not try to install a mux when the connection failed - MINOR : dns: remove irrelevant dependency on a client connection --- 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.