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.1.2 was issued on 2019/12/21.  There are currently 44 patches in 
the queue cut down this way:
    - 1 MAJOR, first one merged on 2020/01/20
    - 15 MEDIUM, first one merged on 2020/01/09
    - 28 MINOR, first one merged on 2020/01/07

Thus the computed ideal release date for 2.1.3 would be 2020/02/03, which was 
within the last week.

The current list of patches in the queue is:
    - MAJOR   : hashes: fix the signedness of the hash inputs
    - MEDIUM  : netscaler: Don't forget to allocate storage for conn->src/dst.
    - MEDIUM  : 0rtt: Only consider the SSL handshake.
    - MEDIUM  : checks: Only attempt to do handshakes if the connection is 
ready.
    - MEDIUM  : tasks: Use the MT macros in tasklet_free().
    - MEDIUM  : cli: _getsocks must send the peers sockets
    - MEDIUM  : mux_h1: Don't call h1_send if we subscribed().
    - MEDIUM  : mux-h2: don't stop sending when crossing a buffer boundary
    - MEDIUM  : session: do not report a failure when rejecting a session
    - MEDIUM  : mworker: remain in mworker mode during reload
    - MEDIUM  : http-ana: Truncate the response when a redirect rule is applied
    - MEDIUM  : connections: Hold the lock when wanting to kill a connection.
    - MEDIUM  : mux-h2: fix missing test on sending_list in previous patch
    - MEDIUM  : connection: add a mux flag to indicate splice usability
    - MEDIUM  : mux-h2: make sure we don't emit TE headers with anything but 
"trailers"
    - MEDIUM  : ssl: Don't forget to free ctx->ssl on failure.
    - MINOR   : checks: refine which errno values are really errors.
    - MINOR   : ssl/cli: ocsp_issuer must be set w/ "set ssl cert"
    - MINOR   : ssl: ssl_sock_load_issuer_file_into_ckch memory leak
    - MINOR   : mux-h2: use a safe list_for_each_entry in h2_send()
    - MINOR   : 51d: Fix bug when HTX is enabled
    - MINOR   : http_act: don't check capture id in backend
    - MINOR   : stream-int: Don't trigger L7 retry if max retries is already 
reached
    - MINOR   : channel: inject output data at the end of output
    - MINOR   : dns: Make dns_query_id_seed unsigned
    - MINOR   : tcpchecks: fix the connect() flags regarding delayed ack
    - MINOR   : h1: Report the right error position when a header value is 
invalid
    - MINOR   : stick-table: Use MAX_SESS_STKCTR as the max track ID during 
parsing
    - MINOR   : ssl/cli: free the previous ckch content once a PEM is loaded
    - MINOR   : ssl: ssl_sock_load_pem_into_ckch is not consistent
    - MINOR   : pattern: handle errors from fgets when trying to load patterns
    - MINOR   : ssl: ssl_sock_load_sctl_from_file memory leak
    - MINOR   : tcp-rules: Fix memory releases on error path during action 
parsing
    - MINOR   : http-ana/filters: Wait end of the http_end callback for all 
filters
    - MINOR   : stream: don't mistake match rules for store-request rules
    - MINOR   : stktable: report the current proxy name in error messages
    - MINOR   : ssl: increment issuer refcount if in chain
    - MINOR   : proxy: Fix input data copy when an error is captured
    - MINOR   : ssl: ssl_sock_load_ocsp_response_from_file memory leak
    - MINOR   : ssl: memory leak w/ the ocsp_issuer
    - MINOR   : ssl: typo in previous patch
    - MINOR   : http-rules: Remove buggy deinit functions for HTTP rules
    - MINOR   : cache: Fix leak of cache name in error path
    - MINOR   : cli/mworker: can't start haproxy with 2 programs

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