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 2.3.0 was issued on 2020-11-05. There are currently 2 patches
in the queue cut down this way:
- 1 MEDIUM, first one merged on 2020-11-06
- 1 MINOR, first one merged on 2020-11-06
Thus the computed ideal release date for 2.3.1 would be 2020-12-04, which is in
four weeks or less.
Last release 2.2.5 was issued on 2020-11-05. There are currently 3 patches
in the queue cut down this way:
- 3 MINOR, first one merged on 2020-11-06
Thus the computed ideal release date for 2.2.6 would be 2020-12-04, which is in
four weeks or less.
Last release 2.1.10 was issued on 2020-11-05. There are currently 1
patches in the queue cut down this way:
- 1 MINOR, first one merged on 2020-11-06
Thus the computed ideal release date for 2.1.11 would be 2020-12-04, which is
in four weeks or less.
The current list of patches in the queue is:
- 2.3 - MEDIUM : ssl/crt-list: correctly insert
crt-list line if crt already loaded
- 2.1, 2.2 - MINOR : http-htx: Just warn if payload of an
errorfile doesn't match the C-L
- 2.2 - MINOR : ssl: double free w/
smp_fetch_ssl_x_chain_der()
- 2.2, 2.3 - MINOR : ssl: don't report 1024 bits DH param
load error when it's higher
--
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.
