stable-bot: WARNING: 32 bug fixes in queue for next release - 2.0
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.12 was issued on 2019/12/21. There are currently 32 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020/01/20 - 12 MEDIUM, first one merged on 2020/01/09 - 19 MINOR, first one merged on 2020/01/09 Thus the computed ideal release date for 2.0.13 would be 2020/02/03, which was within the last week. The current list of patches in the queue is: - MAJOR : hashes: fix the signedness of the hash inputs - MEDIUM : mworker: remain in mworker mode during reload - MEDIUM : connections: Hold the lock when wanting to kill a connection. - MEDIUM : cli: _getsocks must send the peers sockets - MEDIUM : http-ana: Truncate the response when a redirect rule is applied - MEDIUM : 0rtt: Only consider the SSL handshake. - MEDIUM : mux-h2: make sure we don't emit TE headers with anything but "trailers" - MEDIUM : checks: Only attempt to do handshakes if the connection is ready. - MEDIUM : mux_h1: Don't call h1_send if we subscribed(). - MEDIUM : mux-h2: fix missing test on sending_list in previous patch - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : mux-h2: don't stop sending when crossing a buffer boundary - MEDIUM : connection: add a mux flag to indicate splice usability - MINOR : checks: refine which errno values are really errors. - MINOR : http-rules: Remove buggy deinit functions for HTTP rules - MINOR : dns: Make dns_query_id_seed unsigned - MINOR : tcp-rules: Fix memory releases on error path during action parsing - MINOR : pattern: handle errors from fgets when trying to load patterns - MINOR : stktable: report the current proxy name in error messages - MINOR : cli/mworker: can't start haproxy with 2 programs - MINOR : proxy: Fix input data copy when an error is captured - MINOR : cache: Fix leak of cache name in error path - MINOR : http_act: don't check capture id in backend - MINOR : mux-h2: use a safe list_for_each_entry in h2_send() - MINOR : channel: inject output data at the end of output - MINOR : dns: allow srv record weight set to 0 - MINOR : stick-table: Use MAX_SESS_STKCTR as the max track ID during parsing - MINOR : http-ana/filters: Wait end of the http_end callback for all filters - MINOR : 51d: Fix bug when HTX is enabled - MINOR : stream-int: Don't trigger L7 retry if max retries is already reached - MINOR : h1: Report the right error position when a header value is invalid - MINOR : stream: don't mistake match rules for store-request rules --- 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.
stable-bot: WARNING: 32 bug fixes in queue for next release - 2.0
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.12 was issued on 2019/12/21. There are currently 32 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020/01/20 - 12 MEDIUM, first one merged on 2020/01/09 - 19 MINOR, first one merged on 2020/01/09 Thus the computed ideal release date for 2.0.13 would be 2020/02/03, which is in one week or less. The current list of patches in the queue is: - MAJOR : hashes: fix the signedness of the hash inputs - MEDIUM : mworker: remain in mworker mode during reload - MEDIUM : mux-h2: fix missing test on sending_list in previous patch - MEDIUM : 0rtt: Only consider the SSL handshake. - MEDIUM : cli: _getsocks must send the peers sockets - MEDIUM : mux_h1: Don't call h1_send if we subscribed(). - MEDIUM : mux-h2: don't stop sending when crossing a buffer boundary - MEDIUM : http-ana: Truncate the response when a redirect rule is applied - MEDIUM : session: do not report a failure when rejecting a session - MEDIUM : connections: Hold the lock when wanting to kill a connection. - MEDIUM : mux-h2: make sure we don't emit TE headers with anything but "trailers" - MEDIUM : checks: Only attempt to do handshakes if the connection is ready. - MEDIUM : connection: add a mux flag to indicate splice usability - MINOR : tcp-rules: Fix memory releases on error path during action parsing - MINOR : http_act: don't check capture id in backend - MINOR : dns: Make dns_query_id_seed unsigned - MINOR : cli/mworker: can't start haproxy with 2 programs - MINOR : 51d: Fix bug when HTX is enabled - MINOR : stream: don't mistake match rules for store-request rules - MINOR : channel: inject output data at the end of output - MINOR : pattern: handle errors from fgets when trying to load patterns - MINOR : checks: refine which errno values are really errors. - MINOR : http-ana/filters: Wait end of the http_end callback for all filters - MINOR : stream-int: Don't trigger L7 retry if max retries is already reached - MINOR : h1: Report the right error position when a header value is invalid - MINOR : stktable: report the current proxy name in error messages - MINOR : mux-h2: use a safe list_for_each_entry in h2_send() - MINOR : cache: Fix leak of cache name in error path - MINOR : dns: allow srv record weight set to 0 - MINOR : stick-table: Use MAX_SESS_STKCTR as the max track ID during parsing - MINOR : proxy: Fix input data copy when an error is captured - MINOR : http-rules: Remove buggy deinit functions for HTTP rules --- 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.
