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.7 was issued on 2021-03-16. There are currently 6 patches
in the queue cut down this way:
- 1 BUG, first one merged on 2021-03-23
- 3 MEDIUM, first one merged on 2021-03-22
- 2 MINOR, first one merged on 2021-03-18
Thus the computed ideal release date for 2.3.8 would be 2021-04-15, which is in
three weeks or less.
Last release 2.2.11 was issued on 2021-03-18. There are currently 3
patches in the queue cut down this way:
- 1 BUG, first one merged on 2021-03-23
- 2 MEDIUM, first one merged on 2021-03-23
Thus the computed ideal release date for 2.2.12 would be 2021-04-20, which is
in four weeks or less.
The current list of patches in the queue is:
- 2.2, 2.3 - BUG : mworker/cli: do not use the unix_bind
prefix for the master CLI socket
- 2.3 - MEDIUM : mux-fcgi: Fix locking of idle_conns
lock in the FCGI I/O callback
- 2.2, 2.3 - MEDIUM : debug/lua: Don't dump the lua stack if
not dumpable
- 2.2, 2.3 - MEDIUM : freq_ctr/threads: use the
global_now_ms variable
- 2.3 - MINOR : protocol: add missing support of dgram
unix socket.
- 2.3 - MINOR : freq_ctr/threads: make use of the last
updated global time
--
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.
