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.0.12 was issued on 2019/12/21.  There are currently 9 patches in 
the queue cut down this way:
    - 4 MEDIUM, first one merged on 2020/01/09
    - 5 MINOR, first one merged on 2020/01/09

Thus the computed ideal release date for 2.0.13 would be 2020/02/06, which is 
in four weeks or less.

The current list of patches in the queue is:
    - MEDIUM  : http-ana: Truncate the response when a redirect rule is applied
    - MEDIUM  : connections: Hold the lock when wanting to kill a connection.
    - MEDIUM  : checks: Only attempt to do handshakes if the connection is 
ready.
    - MEDIUM  : session: do not report a failure when rejecting a session
    - MINOR   : channel: inject output data at the end of output
    - MINOR   : proxy: Fix input data copy when an error is captured
    - MINOR   : h1: Report the right error position when a header value is 
invalid
    - MINOR   : checks: refine which errno values are really errors.
    - MINOR   : stream-int: Don't trigger L7 retry if max retries is already 
reached

---
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.

Reply via email to