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.2.4 was issued on 2020-09-30. There are currently 11 patches in the queue cut down this way: - 3 MEDIUM, first one merged on 2020-10-02 - 8 MINOR, first one merged on 2020-10-02 Thus the computed ideal release date for 2.2.5 would be 2020-10-30, which is in three weeks or less. Last release 2.1.9 was issued on 2020-09-30. There are currently 9 patches in the queue cut down this way: - 4 MEDIUM, first one merged on 2020-09-30 - 5 MINOR, first one merged on 2020-10-08 Thus the computed ideal release date for 2.1.10 would be 2020-10-30, which is in three weeks or less. Last release 2.0.18 was issued on 2020-09-30. There are currently 7 patches in the queue cut down this way: - 2 MEDIUM, first one merged on 2020-10-08 - 5 MINOR, first one merged on 2020-10-08 Thus the computed ideal release date for 2.0.19 would be 2020-12-03, which is in seven weeks or less. Last release 1.8.26 was issued on 2020-08-03. There are currently 18 patches in the queue cut down this way: - 8 MEDIUM, first one merged on 2020-08-05 - 10 MINOR, first one merged on 2020-08-03 Thus the computed ideal release date for 1.8.27 would be 2020-10-26, which is in two weeks or less. The current list of patches in the queue is: - 2.0, 2.1, 2.2 - MEDIUM : mux-h2: Don't handle pending read0 too early on streams - 1.8 - MEDIUM : h2: report frame bits only for handled types - 2.1, 2.2 - MEDIUM : mux-fcgi: Don't handle pending read0 too early on streams - 2.1 - MEDIUM : ssl: crt-list negative filters don't work - 1.8 - MEDIUM : ssl: check OCSP calloc in ssl_sock_load_ocsp() - 1.8 - MEDIUM : pattern: fix memory leak in regex pattern functions - 1.8 - MEDIUM : map/lua: Return an error if a map is loaded during runtime - 1.8 - MEDIUM : pattern: Renew the pattern expression revision when it is pruned - 1.8 - MEDIUM : mux-h2: Don't fail if nothing is parsed for a legacy chunk response - 1.8 - MEDIUM : ssl: does not look for all SNIs before chosing a certificate - 1.8 - MEDIUM : listeners: do not pause foreign listeners - 2.0, 2.1, 2.2 - MEDIUM : queue: make pendconn_cond_unlink() really thread-safe - 1.8 - MINOR : stats: use strncmp() instead of memcmp() on health states - 2.2 - MINOR : http: Fix content-length of the default 500 error - 1.8 - MINOR : startup: haproxy -s cause 100% cpu - 1.8 - MINOR : config: Fix memory leak on config parse listen - 1.8, 2.0, 2.1, 2.2 - MINOR : stats: fix validity of the json schema - 2.0, 2.1, 2.2 - MINOR : http-htx: Expect no body for 204/304 internal HTTP responses - 1.8 - MINOR : ssl: verifyhost is case sensitive - 2.0, 2.1, 2.2 - MINOR : peers: Inconsistency when dumping peer status codes. - 1.8 - MINOR : lua: Check argument type to convert it to IP mask in arg validation - 1.8 - MINOR : dns: ignore trailing dot - 1.8 - MINOR : threads: work around a libgcc_s issue with chrooting - 1.8 - MINOR : lua: Check argument type to convert it to IPv4/IPv6 arg validation - 2.0, 2.1, 2.2 - MINOR : mux-h1: Always set the session on frontend h1 stream - 2.2 - MINOR : mux-h1: Be sure to only set CO_RFL_READ_ONCE for the first read - 1.8 - MINOR : reload: do not fail when no socket is sent - 2.2 - MINOR : tcpcheck: Set socks4 and send-proxy flags before the connect call - 2.0, 2.1, 2.2 - MINOR : Fix several leaks of 'log_tag' in init(). -- 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.