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.13 was issued on 2018/07/30. There are currently 16 patches
in the queue cut down this way:
- 13 MEDIUM, first one merged on 2018/08/07
- 3 MINOR, first one merged on 2018/08/24
Thus the computed ideal release date for 1.8.14 would be 2018/09/06, which is
in one week or less.
The current list of patches in the queue is:
- MEDIUM : threads: fix the no-thread case after the change to the sync
point
- MEDIUM : unix: provide a ->drain() function
- MEDIUM : servers: check the queues once enabling a server
- MEDIUM : lua: socket timeouts are not applied
- MEDIUM : cli: make "show fd" thread-safe
- MEDIUM : cli/threads: protect some server commands against concurrent
operations
- MEDIUM : threads: fix the double CAS implementation for ARMv7
- MEDIUM : lua: possible CLOSE-WAIT state with '\n' headers
- MEDIUM : mux_pt: dereference the connection with care in mux_pt_wake()
- MEDIUM : cli/threads: protect all "proxy" commands against concurrent
updates
- MEDIUM : ssl: fix missing error loading a keytype cert from a bundle.
- MEDIUM : queue: prevent a backup server from draining the proxy's
connections
- MEDIUM : ssl: loading dh param from certifile causes unpredictable error.
- MINOR : map: fix map_regm with backref
- MINOR : ssl: empty connections reported as errors.
- MINOR : lua: Bad HTTP client request duration.
---
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.
