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.4 was issued on 2019/02/06.  There are currently 42 patches in 
the queue cut down this way:
    - 1 BUG, first one merged on 2019/02/10
    - 6 MAJOR, first one merged on 2019/02/10
    - 20 MEDIUM, first one merged on 2019/02/10
    - 15 MINOR, first one merged on 2019/02/10

Thus the computed ideal release date for 1.9.5 would be 2019/02/24, which was 
two weeks ago.

The current list of patches in the queue is:
    - BUG     : 51d: In Hash Trie, multi header matching was affected by the 
header names stored globaly.
    - MAJOR   : listener: Make sure the listener exist before using it.
    - MAJOR   : cache/htx: Set the start-line offset when a cached object is 
served
    - MAJOR   : mux-h2: fix race condition between close on both ends
    - MAJOR   : spoe: Don't try to get agent config during SPOP healthcheck
    - MAJOR   : fd/threads, task/threads: ensure all spin locks are unlocked
    - MAJOR   : stream: avoid double free on unique_id
    - MEDIUM  : htx: count the amount of copied data towards the final count
    - MEDIUM  : logs: Only attempt to free startup_logs once.
    - MEDIUM  : server: initialize the idle conns list after parsing the config
    - MEDIUM  : server: initialize the orphaned conns lists and tasks at the end
    - MEDIUM  : mux-h1: Report the right amount of data xferred in h1_rcv_buf()
    - MEDIUM  : proto_htx: Fix functions applying regex filters on HTX messages
    - MEDIUM  : h2/htx: verify that :path doesn't contain invalid chars
    - MEDIUM  : cache: Get objects from the cache only for GET and HEAD requests
    - MEDIUM  : h2/htx: Correctly handle interim responses when HTX is enabled
    - MEDIUM  : proto_htx: Fix data size update if end of the cookie is removed
    - MEDIUM  : http_fetch: fix the "base" and "base32" fetch methods in HTX 
mode
    - MEDIUM  : servers: Add a per-thread counter of idle connections.
    - MEDIUM  : listeners: Don't call fd_stop_recv() if fd_updt is NULL.
    - MEDIUM  : 51d: fix possible segfault on deinit_51degrees()
    - MEDIUM  : servers: Use atomic operations when handling curr_idle_conns.
    - MEDIUM  : h2: advertise to servers that we don't support push
    - MEDIUM  : mux-h2/htx: send an empty DATA frame on empty HTX trailers
    - MEDIUM  : http_fetch: fix "req.body_len" and "req.body_size" fetch 
methods in HTX mode
    - MEDIUM  : spoe: initialization depending on nbthread must be done last
    - MEDIUM  : mux-h2/htx: Always set CS flags before exiting h2_rcv_buf()
    - MINOR   : ssl: fix warning about ssl-min/max-ver support
    - MINOR   : channel: Set CF_WROTE_DATA when outgoing data are skipped
    - MINOR   : lua: initialize the correct idle conn lists for the SSL sockets
    - MINOR   : checks: make external-checks restore the original 
rlim_fd_cur/max
    - MINOR   : config: Reinforce validity check when a process number is parsed
    - MINOR   : mux-h2: Don't add ":status" pseudo-header on trailers
    - MINOR   : spoe: do not assume agent->rt is valid on exit
    - MINOR   : mux-h1: Add "transfer-encoding" header on outgoing requests if 
needed
    - MINOR   : listener: keep accept rate counters accurate under saturation
    - MINOR   : mworker: be careful to restore the original rlim_fd_cur/max on 
reload
    - MINOR   : proto-htx: Consider a XFER_LEN message as chunked by default
    - MINOR   : mux-h1: verify the request's version before dropping 
connection: keep-alive
    - MINOR   : init: never lower rlim_fd_max
    - MINOR   : cache/htx: Return only the headers of cached objects to HEAD 
requests
    - MINOR   : mux-h1: Always initilize h1m variable in h1_process_input()

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