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.10 was issued on 2019/11/25. There are currently 13 patches
in the queue cut down this way:
- 5 MEDIUM, first one merged on 2019/12/05
- 8 MINOR, first one merged on 2019/11/25
Thus the computed ideal release date for 2.0.11 would be 2019/12/23, which is
in two weeks or less.
The current list of patches in the queue is:
- MEDIUM : checks: Make sure we set the task affinity just before
connecting.
- MEDIUM : stream-int: don't subscribed for recv when we're trying to
flush data
- MEDIUM : tasks: Make sure we switch wait queues in task_set_affinity().
- MEDIUM : listener/thread: fix a race when pausing a listener
- MEDIUM : mux-h1: Never reuse H1 connection if a shutw is pending
- MINOR : contrib/prometheus-exporter: decode parameter and value only
- MINOR : mux-h1: Fix conditions to know whether or not we may receive
data
- MINOR : stream-int: avoid calling rcv_buf() when splicing is still
possible
- MINOR : stream: init variables when the list is empty
- MINOR : contrib/prometheus-exporter: Use HTX errors and not legacy ones
- MINOR : mux-h1: Don't rely on CO_FL_SOCK_RD_SH to set H1C_F_CS_SHUTDOWN
- MINOR : http-htx: Don't make http_find_header() fail if the value is
empty
- MINOR : ssl: certificate choice can be unexpected with 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.
