unsubscribe On Sat, Jun 15, 2019, 5:02 PM <stable-...@haproxy.com> wrote:
> 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.20 was issued on 2019/04/25. There are currently 11 > patches in the queue cut down this way: > - 2 MAJOR, first one merged on 2019/04/30 > - 6 MEDIUM, first one merged on 2019/04/29 > - 3 MINOR, first one merged on 2019/04/29 > > Thus the computed ideal release date for 1.8.21 would be 2019/05/14, which > was four weeks ago. > > The current list of patches in the queue is: > - MAJOR : map/acl: real fix segfault during show map/acl on CLI > - MAJOR : lb/threads: make sure the avoided server is not full on > second pass > - MEDIUM : listener: Fix how unlimited number of consecutive accepts > is handled > - MEDIUM : spoe: Don't use the SPOE applet after releasing it > - MEDIUM : port_range: Make the ring buffer lock-free. > - MEDIUM : contrib/modsecurity: If host header is NULL, don't try to > strdup it > - MEDIUM : spoe: arg len encoded in previous frag frame but len > changed > - MEDIUM : dns: make the port numbers unsigned > - MINOR : ssl_sock: Fix memory leak when disabling compression > - MINOR : http_fetch: Rely on the smp direction for "cookie()" and > "hdr()" > - MINOR : http: Call stream_inc_be_http_req_ctr() only one time per > request > > --- > 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. > >
