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 1.8.19 was issued on 2019/02/11. There are currently 7 patches in
the queue cut down this way:
- 2 MAJOR, first one merged on 2019/03/11
- 3 MEDIUM, first one merged on 2019/03/11
- 2 MINOR, first one merged on 2019/03/11
Thus the computed ideal release date for 1.8.20 would be 2019/03/25, which was
four weeks ago.
The current list of patches in the queue is:
- MAJOR : listener: Make sure the listener exist before using it.
- MAJOR : spoe: Fix initialization of thread-dependent fields
- MEDIUM : threads/fd: do not forget to take into account epoll_fd/pipes
- MEDIUM : 51d: fix possible segfault on deinit_51degrees()
- MEDIUM : logs: Only attempt to free startup_logs once.
- MINOR : listener: keep accept rate counters accurate under saturation
- MINOR : ssl: fix warning about ssl-min/max-ver support
---
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.
