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.4 was issued on 2021-01-13. There are currently 16
patches in the queue cut down this way:
- 6 MEDIUM, first one merged on 2021-01-26
- 10 MINOR, first one merged on 2021-01-26
Thus the computed ideal release date for 2.3.5 would be 2021-02-23, which is in
three weeks or less.
Last release 2.2.8 was issued on 2021-01-13. There are currently 10
patches in the queue cut down this way:
- 3 MEDIUM, first one merged on 2021-01-26
- 7 MINOR, first one merged on 2021-01-26
Thus the computed ideal release date for 2.2.9 would be 2021-02-23, which is in
three weeks or less.
Last release 2.1.11 was issued on 2021-01-08. There are currently 11
patches in the queue cut down this way:
- 3 MEDIUM, first one merged on 2021-01-26
- 8 MINOR, first one merged on 2021-01-26
Thus the computed ideal release date for 2.1.12 would be 2021-03-23, which is
in seven weeks or less.
Last release 2.0.20 was issued on 2021-01-08. There are currently 8
patches in the queue cut down this way:
- 3 MEDIUM, first one merged on 2021-01-28
- 5 MINOR, first one merged on 2021-01-28
Thus the computed ideal release date for 2.0.21 would be 2021-03-25, which is
in seven weeks or less.
The current list of patches in the queue is:
- 2.3 - MEDIUM : tcpcheck: Don't destroy connection in
the wake callback context
- 2.3 - MEDIUM : session: only retrieve ready idle conn
from session
- 2.0, 2.1, 2.2, 2.3 - MEDIUM : mux-h2: fix read0 handling on
partial frames
- 2.0, 2.1, 2.2, 2.3 - MEDIUM : stats: add missing INF_BUILD_INFO
definition
- 2.0, 2.1, 2.2, 2.3 - MEDIUM : filters/htx: Fix data forwarding
when payload length is unknown
- 2.3 - MEDIUM : backend: never reuse a connection for
tcp mode
- 2.2, 2.3 - MINOR : peers: Possible appctx pointer
dereference.
- 2.0, 2.1, 2.2, 2.3 - MINOR : peers: Wrong "new_conn" value for
"show peers" CLI command.
- 2.1, 2.2, 2.3 - MINOR : threads: Fixes the number of possible
cpus report for Mac.
- 2.1, 2.2, 2.3 - MINOR : mux_h2: missing space between "st" and
".flg" in the "show fd" helper
- 2.0, 2.1 - MINOR : sample: Memory leak of sample_expr
structure in case of error
- 2.0, 2.1, 2.2, 2.3 - MINOR : init: Use a dynamic buffer to set
HAPROXY_CFGFILES env variable
- 2.0, 2.1 - MINOR : sample: check alloc_trash_chunk return
value in concat()
- 2.1 - MINOR : init: enforce strict-limits when using
master-worker
- 2.3 - MINOR : config: fix leak on
proxy.conn_src.bind_hdr_name
- 2.3 - MINOR : backend: check available list
allocation for reuse
- 2.2, 2.3 - MINOR : dns: SRV records ignores duplicated AR
records (v2)
- 2.0, 2.1, 2.2, 2.3 - MINOR : mworker: define _GNU_SOURCE for
strsignal()
- 2.3 - MINOR : ssl: init tmp chunk correctly in
ssl_sock_load_sctl_from_file()
--
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.
