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.17 was issued on 2019/01/08. There are currently 10 patches
in the queue cut down this way:
- 1 MAJOR, first one merged on 2019/01/28
- 3 MEDIUM, first one merged on 2019/01/28
- 6 MINOR, first one merged on 2019/01/28
Thus the computed ideal release date for 1.8.18 would be 2019/02/11, which is
in one week or less.
The current list of patches in the queue is:
- MAJOR : cache: fix confusion between zero and uninitialized cache key
- MEDIUM : ssl: missing allocation failure checks loading tls key file
- MEDIUM : ssl: Fix handling of TLS 1.3 KeyUpdate messages
- MEDIUM : ssl: Disable anti-replay protection and set max data with 0RTT.
- MINOR : server: don't always trust srv_check_health when loading a
server state
- MINOR : check: Wake the check task if the check is finished in
wake_srv_chk()
- MINOR : stick_table: Prevent conn_cur from underflowing
- MINOR : backend: BE_LB_LKUP_CHTREE is a value, not a bit
- MINOR : backend: don't use url_param_name as a hint for BE_LB_ALGO_PH
- MINOR : backend: balance uri specific options were lost across defaults
---
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.
