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.11 was issued on 2021-03-18. There are currently 8
patches in the queue cut down this way:
- 1 BUG, first one merged on 2021-03-23
- 6 MEDIUM, first one merged on 2021-03-23
- 1 MINOR, first one merged on 2021-03-24
Thus the computed ideal release date for 2.2.12 would be 2021-04-20, which is
in three weeks or less.
Last release 2.0.21 was issued on 2021-03-18. There are currently 4
patches in the queue cut down this way:
- 1 BUG, first one merged on 2021-03-24
- 3 MEDIUM, first one merged on 2021-03-24
Thus the computed ideal release date for 2.0.22 would be 2021-05-19, which is
in seven weeks or less.
The current list of patches in the queue is:
- 2.0, 2.2 - BUG : mworker/cli: do not use the unix_bind
prefix for the master CLI socket
- 2.2 - MEDIUM : fd: do not wait on FD removal in
fd_delete()
- 2.0, 2.2 - MEDIUM : lua: Always init the lua stack before
referencing the context
- 2.0, 2.2 - MEDIUM : freq_ctr/threads: use the
global_now_ms variable
- 2.2 - MEDIUM : debug/lua: Don't dump the lua stack if
not dumpable
- 2.2 - MEDIUM : fd: Take the fd_mig_lock when closing
if no DWCAS is available.
- 2.0, 2.2 - MEDIUM : debug/lua: Use internal hlua function
to dump the lua traceback
- 2.2 - MINOR : ssl: Prevent disk access when using
"add ssl crt-list"
--
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.
