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.9 was issued on 2019/11/15. There are currently 13 patches in
the queue cut down this way:
- 1 BUILD, first one merged on 2019/11/20
- 2 MEDIUM, first one merged on 2019/11/19
- 10 MINOR, first one merged on 2019/11/19
Thus the computed ideal release date for 2.0.10 would be 2019/12/17, which is
in four weeks or less.
The current list of patches in the queue is:
- BUILD : debug: Avoid warnings in dev mode with -02 because of some
BUG_ON tests
- MEDIUM : stream-int: Don't loose events on the CS when an EOS is reported
- MEDIUM : mworker: don't fill the -sf argument with -1 during the reexec
- MINOR : mux-h1: Fix tunnel mode detection on the response path
- MINOR : contrib/prometheus-exporter: Rename some metrics
- MINOR : peers: Wrong null "server_name" data field handling.
- MINOR : stream-int: Fix si_cs_recv() return value
- MINOR : peers: "peer alive" flag not reset when deconnecting.
- MINOR : init: fix set-dumpable when using uid/gid
- MINOR : mux-h1: Fix a UAF in cfg_h1_headers_case_adjust_postparser()
- MINOR : http-ana: Properly catch aborts during the payload forwarding
- MINOR : mux-h1: Adjust header case when chunked encoding is add to a
message
- MINOR : ssl: fix crt-list neg filter for openssl < 1.1.1
---
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.
