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.21 was issued on 2019/08/16. There are currently 7 patches in
the queue cut down this way:
- 4 MEDIUM, first one merged on 2019/08/23
- 3 MINOR, first one merged on 2019/08/23
Thus the computed ideal release date for 1.8.22 would be 2019/09/20, which is
in three weeks or less.
The current list of patches in the queue is:
- MEDIUM : ssl: Use the early_data API the right way.
- MEDIUM : checks: make sure the warmup task takes the server lock
- MEDIUM : listener/threads: fix an AB/BA locking issue in
delete_listener()
- MEDIUM : spoe: Be sure the sample is found before setting its context
- MINOR : logs/threads: properly split the log area upon startup
- MINOR : haproxy: fix rule->file memory leak
- MINOR : mworker: disable SIGPROF on re-exec
---
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.
