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.2.4 was issued on 2020-09-30. There are currently 40
patches in the queue cut down this way:
- 1 MAJOR, first one merged on 2020-10-22
- 12 MEDIUM, first one merged on 2020-10-02
- 27 MINOR, first one merged on 2020-10-02
Thus the computed ideal release date for 2.2.5 would be 2020-10-30, which was
within the last week.
Last release 2.1.9 was issued on 2020-09-30. There are currently 35
patches in the queue cut down this way:
- 1 MAJOR, first one merged on 2020-11-03
- 13 MEDIUM, first one merged on 2020-09-30
- 21 MINOR, first one merged on 2020-10-08
Thus the computed ideal release date for 2.1.10 would be 2020-10-30, which was
within the last week.
Last release 2.0.18 was issued on 2020-09-30. There are currently 30
patches in the queue cut down this way:
- 1 MAJOR, first one merged on 2020-11-03
- 11 MEDIUM, first one merged on 2020-10-08
- 18 MINOR, first one merged on 2020-10-08
Thus the computed ideal release date for 2.0.19 would be 2020-12-01, which is
in four weeks or less.
Last release 1.8.26 was issued on 2020-08-03. There are currently 20
patches in the queue cut down this way:
- 10 MEDIUM, first one merged on 2020-08-05
- 10 MINOR, first one merged on 2020-08-03
Thus the computed ideal release date for 1.8.27 would be 2020-10-26, which was
one week ago.
The current list of patches in the queue is:
- 2.0, 2.1, 2.2 - MAJOR : mux-h2: Don't try to send data if we
know it is no longer possible
- 1.8, 2.0, 2.1, 2.2 - MEDIUM : spoe: Unset variable instead of
set it if no data provided
- 2.0, 2.1, 2.2 - MEDIUM : mux-h2: Don't handle pending read0 too
early on streams
- 1.8 - MEDIUM : ssl: check OCSP calloc in
ssl_sock_load_ocsp()
- 1.8 - MEDIUM : listeners: do not pause foreign
listeners
- 1.8 - MEDIUM : h2: report frame bits only for handled
types
- 1.8 - MEDIUM : ssl: does not look for all SNIs before
chosing a certificate
- 1.8 - MEDIUM : pattern: fix memory leak in regex
pattern functions
- 1.8 - MEDIUM : map/lua: Return an error if a map is
loaded during runtime
- 1.8 - MEDIUM : pattern: Renew the pattern expression
revision when it is pruned
- 2.0, 2.1, 2.2 - MEDIUM : task: bound the number of tasks picked
from the wait queue at once
- 2.1, 2.2 - MEDIUM : mux-fcgi: Don't handle pending read0
too early on streams
- 2.1, 2.2 - MEDIUM : ssl: OCSP must work with BoringSSL
- 2.0, 2.1, 2.2 - MEDIUM : filters: Don't try to init filters for
disabled proxies
- 1.8, 2.0, 2.1, 2.2 - MEDIUM : lb: Always lock the server when
calling server_{take,drop}_conn
- 2.0, 2.1, 2.2 - MEDIUM : mux-pt: Release the tasklet during an
HTTP upgrade
- 2.0, 2.1, 2.2 - MEDIUM : stick-table: limit the time spent
purging old entries
- 2.0, 2.1, 2.2 - MEDIUM : server: support changing the slowstart
value from state-file
- 2.0, 2.1, 2.2 - MEDIUM : mux-h1: Get the session from the H1S
when capturing bad messages
- 2.1 - MEDIUM : ssl: crt-list negative filters don't
work
- 2.0 - MEDIUM : h1: Always try to receive more in
h1_rcv_buf().
- 2.0, 2.1, 2.2 - MEDIUM : queue: make pendconn_cond_unlink()
really thread-safe
- 1.8 - MEDIUM : mux-h2: Don't fail if nothing is
parsed for a legacy chunk response
- 2.0, 2.1, 2.2 - MINOR : extcheck: add missing checks on
extchk_setenv()
- 2.0, 2.1, 2.2 - MINOR : server: Set server without addr but
with dns in RMAINT on startup
- 2.0, 2.1, 2.2 - MINOR : init: only keep rlim_fd_cur if max is
unlimited
- 2.0, 2.1, 2.2 - MINOR : server: fix down_time report for stats
- 2.0, 2.1, 2.2 - MINOR : Fix several leaks of 'log_tag' in
init().
- 2.0, 2.1, 2.2 - MINOR : mux-h1: Always set the session on
frontend h1 stream
- 2.2 - MINOR : connection: fix loop iter on
connection takeover
- 1.8 - MINOR : lua: Check argument type to convert it
to IPv4/IPv6 arg validation
- 2.2 - MINOR : mux-h1: Be sure to only set
CO_RFL_READ_ONCE for the first read
- 2.0, 2.1, 2.2 - MINOR : peers: Possible unexpected peer
seesion reset after collisions.
- 2.2 - MINOR : tcpcheck: Set socks4 and send-proxy
flags before the connect call
- 1.8 - MINOR : threads: work around a libgcc_s issue
with chrooting
- 2.0, 2.1, 2.2 - MINOR : http-htx: Expect no body for 204/304
internal HTTP responses
- 1.8 - MINOR : startup: haproxy -s cause 100% cpu
- 2.2 - MINOR : log: fix risk of null deref on error
path
- 2.0, 2.1, 2.2 - MINOR : peers: Inconsistency when dumping peer
status codes.
- 1.8 - MINOR : config: Fix memory leak on config
parse listen
- 2.0, 2.1, 2.2 - MINOR : cache: Inverted variables in
http_calc_maxage function
- 2.0, 2.1, 2.2 - MINOR : queue: properly report redistributed
connections
- 2.1, 2.2 - MINOR : cache: Manage multiple values in
cache-control header value
- 2.0, 2.1, 2.2 - MINOR : http-ana: Don't send payload for
internal responses to HEAD requests
- 2.2 - MINOR : checks: Report a socket error before
any connection attempt
- 1.8, 2.0, 2.1, 2.2 - MINOR : stats: fix validity of the json
schema
- 1.8 - MINOR : dns: ignore trailing dot
- 2.1, 2.2 - MINOR : disable dynamic OCSP load with
BoringSSL
- 1.8 - MINOR : lua: Check argument type to convert it
to IP mask in arg validation
- 2.2 - MINOR : http: Fix content-length of the
default 500 error
- 2.0, 2.1, 2.2 - MINOR : log: fix memory leak on logsrv parse
error
- 2.0, 2.1, 2.2 - MINOR : lua: initialize sample before using it
- 2.0, 2.1, 2.2 - MINOR : mux-h2: do not stop outgoing
connections on stopping
- 1.8 - MINOR : ssl: verifyhost is case sensitive
- 1.8 - MINOR : stats: use strncmp() instead of
memcmp() on health states
- 1.8 - MINOR : reload: do not fail when no socket is
sent
- 2.0, 2.1, 2.2 - MINOR : server: fix srv downtime calcul on
starting
- 2.1, 2.2 - MINOR : proxy/server: Skip per-proxy/server
post-check for disabled proxies
- 2.0, 2.1, 2.2 - MINOR : filters: Skip disabled proxies during
startup only
--
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.
