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.5 was issued on 2019/08/16. There are currently 14 patches in the queue cut down this way: - 8 MEDIUM, first one merged on 2019/08/23 - 6 MINOR, first one merged on 2019/08/26 Thus the computed ideal release date for 2.0.6 would be 2019/09/22, which is in two weeks or less. The current list of patches in the queue is: - MEDIUM : cache: Don't cache objects if the size of headers is too big - MEDIUM : url32 does not take the path part into account in the returned hash. - MEDIUM : peers: local peer socket not bound. - MEDIUM : proto-http: Always start the parsing if there is no outgoing data - MEDIUM : mux-h1: do not report errors on transfers ending on buffer full - MEDIUM : listener/threads: fix an AB/BA locking issue in delete_listener() - MEDIUM : cache: Properly copy headers splitted on several shctx blocks - MEDIUM : mux-h1: do not truncate trailing 0CRLF on buffer boundary - MINOR : mux-h1: Fix size evaluation of HTX messages after headers parsing - MINOR : mux-h1: Don't stop anymore input processing when the max is reached - MINOR : h1: Properly reset h1m when parsing is restarted - MINOR : mux-h1: Be sure to update the count before adding EOM after trailers - MINOR : mworker: disable SIGPROF on re-exec - MINOR : http-ana: Reset response flags when 1xx messages are handled --- 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.