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.9.12 was issued on 2019/10/24. There are currently 13 patches
in the queue cut down this way:
- 1 BUG, first one merged on 2019/11/07
- 1 MAJOR, first one merged on 2019/10/28
- 7 MEDIUM, first one merged on 2019/11/06
- 4 MINOR, first one merged on 2019/10/28
Thus the computed ideal release date for 1.9.13 would be 2019/11/11, which was
within the last week.
The current list of patches in the queue is:
- BUG : dns: timeout resolve not applied for valid resolutions
- MAJOR : stream-int: Don't receive data from mux until SI_ST_EST is
reached
- MEDIUM : stream: Be sure to support splicing at the mux level to enable
it
- MEDIUM : mux-h2: report no available stream on a connection having errors
- MEDIUM : mux-h2: immediately remove a failed connection from the idle
list
- MEDIUM : stream: Be sure to release allocated captures for TCP streams
- MEDIUM : mux-h1: Disable splicing for chunked messages
- MEDIUM : mux-h2: immediately report connection errors on streams
- MEDIUM : servers: Only set SF_SRV_REUSED if the connection if fully
ready.
- MINOR : cli: don't call the kw->io_release if kw->parse failed
- MINOR : config: Update cookie domain warn to RFC6265
- MINOR : mux-h2: do not emit logs on backend connections
- MINOR : spoe: fix off-by-one length in UUID format string
---
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.
