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.3.2 was issued on 2020-11-28. There are currently 23 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2020-12-14 - 6 MEDIUM, first one merged on 2020-12-14 - 15 MINOR, first one merged on 2020-12-14 Thus the computed ideal release date for 2.3.3 would be 2020-12-28, which was within the last week. Last release 2.2.6 was issued on 2020-11-30. There are currently 17 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2020-12-14 - 3 MEDIUM, first one merged on 2020-12-14 - 12 MINOR, first one merged on 2020-12-14 Thus the computed ideal release date for 2.2.7 would be 2020-12-28, which was within the last week. Last release 2.1.10 was issued on 2020-11-05. There are currently 26 patches in the queue cut down this way: - 4 MAJOR, first one merged on 2020-11-13 - 5 MEDIUM, first one merged on 2020-11-13 - 17 MINOR, first one merged on 2020-11-06 Thus the computed ideal release date for 2.1.11 would be 2020-12-11, which was two weeks ago. Last release 2.0.19 was issued on 2020-11-06. There are currently 24 patches in the queue cut down this way: - 4 MAJOR, first one merged on 2020-11-13 - 5 MEDIUM, first one merged on 2020-11-13 - 15 MINOR, first one merged on 2020-11-13 Thus the computed ideal release date for 2.0.20 would be 2020-12-11, which was two weeks ago. The current list of patches in the queue is: - 2.0, 2.1, 2.2, 2.3 - MAJOR : spoa/python: Fixing return None - 2.0, 2.1 - MAJOR : peers: fix partial message decoding - 2.0, 2.1 - MAJOR : filters: Always keep all offsets up to date during data filtering - 2.0, 2.1 - MAJOR : spoe: Be sure to remove all references on a released spoe applet - 2.2, 2.3 - MAJOR : ring: tcp forward on ring can break the reader counter. - 2.0, 2.1, 2.2, 2.3 - MEDIUM : spoa/python: Fixing references to None - 2.0, 2.1, 2.2, 2.3 - MEDIUM : lb-leastconn: Reposition a server using the right eweight - 2.3 - MEDIUM : task: close a possible data race condition on a tasklet's list link - 2.0, 2.1, 2.2, 2.3 - MEDIUM : spoa/python: Fixing PyObject_Call positional arguments - 2.3 - MEDIUM : lists: Lock the element while we check if it is in a list. - 2.3 - MEDIUM : local log format regression. - 2.0, 2.1 - MEDIUM : peers: fix decoding of multi-byte length in stick-table messages - 2.0, 2.1 - MEDIUM : filters: Forward all filtered data at the end of http filtering - 2.0, 2.1, 2.2, 2.3 - MINOR : spoa/python: Cleanup references for failed Module Addobject operations - 2.0, 2.1 - MINOR : peers: Do not ignore a protocol error for dictionary entries. - 2.0, 2.1 - MINOR : peers: Missing TX cache entries reset. - 2.2, 2.3 - MINOR : http-check: Use right condition to consider HTX message as full - 2.0, 2.1, 2.2, 2.3 - MINOR : lua: Some lua init operation are processed unsafe - 2.0, 2.1 - MINOR : lua: set buffer size during map lookups - 2.1 - MINOR : http-htx: Just warn if payload of an errorfile doesn't match the C-L - 2.1, 2.2, 2.3 - MINOR : lua: missing "\n" in error message - 2.3 - MINOR : listener: use sockaddr_in6 for IPv6 - 2.0, 2.1 - MINOR : http-fetch: Fix calls w/o parentheses of the cookie sample fetches - 2.0, 2.1, 2.2, 2.3 - MINOR : lua: lua-load doesn't check its parameters - 2.0, 2.1, 2.2, 2.3 - MINOR : lua: warn when registering action, conv, sf, cli or applet multiple times - 2.0, 2.1 - MINOR : http-ana: Don't wait for the body of CONNECT requests - 2.0, 2.1 - MINOR : http-fetch: Extract cookie value even when no cookie name - 2.2, 2.3 - MINOR : mux-h1: Handle keep-alive timeout for idle frontend connections - 2.0, 2.1, 2.2, 2.3 - MINOR : spoa/python: Cleanup ipaddress objects if initialization fails - 2.0, 2.1 - MINOR : pattern: a sample marked as const could be written - 2.2, 2.3 - MINOR : tcpcheck: Don't rearm the check timeout on each read - 2.0, 2.1, 2.2, 2.3 - MINOR : lua: Post init register function are not executed beyond the first one - 2.0, 2.1, 2.2, 2.3 - MINOR : tools: make parse_time_err() more strict on the timer validity - 2.3 - MINOR : mux-h2/stats: not all GOAWAY frames are errors - 2.3 - MINOR : mux-h2/stats: make stream/connection proto errors more accurate - 2.0, 2.1, 2.2, 2.3 - MINOR : tools: Reject size format not starting by a digit -- 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.