Hi,
This is a friendly bot that watches fixes pending for the next haproxy-stable
release! One such e-mail is sent every week 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.9 was issued on 2018/05/18. There are currently 10 patches in
the queue cut down this way:
- 2 BUILD, first one merged on 2018/05/23
- 6 MEDIUM, first one merged on 2018/05/23
- 2 MINOR, first one merged on 2018/05/23
Thus the computed ideal release date for 1.8.10 would be 2018/06/20, which is
in two weeks or less.
The current list of patches in the queue is:
- BUILD : fd: fix typo causing a warning when threads are disabled
- BUILD : threads: unbreak build without threads
- MEDIUM : spoe: Flags are not encoded in network order
- MEDIUM : fd: Only check update_mask against all_threads_mask.
- MEDIUM : cache: don't cache when an Authorization header is present
- MEDIUM : contrib/mod_defender: Use network order to encode/decode flags
- MEDIUM : dns: Delay the attempt to run a DNS resolution on check failure.
- MEDIUM : contrib/modsecurity: Use network order to encode/decode flags
- MINOR : lua: Socket.send threw runtime error: 'close' needs 1 arguments.
- MINOR : ssl/lua: prevent lua from affecting automatic maxconn
computation
---
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.
