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.2.1 was issued on 2020-07-23.  There are currently 2 patches in 
the queue cut down this way:
    - 2 MINOR, first one merged on 2020-07-23

Thus the computed ideal release date for 2.2.2 would be 2020-08-20, which is in 
three weeks or less.

Last release 2.1.7 was issued on 2020-06-09.  There are currently 48 patches in 
the queue cut down this way:
    - 1 MAJOR, first one merged on 2020-07-23
    - 21 MEDIUM, first one merged on 2020-06-12
    - 26 MINOR, first one merged on 2020-06-12

Thus the computed ideal release date for 2.1.8 would be 2020-07-10, which was 
two weeks ago.

Last release 2.0.16 was issued on 2020-07-17.  There are currently 9 patches in 
the queue cut down this way:
    - 1 MAJOR, first one merged on 2020-07-23
    - 5 MEDIUM, first one merged on 2020-07-21
    - 3 MINOR, first one merged on 2020-07-21

Thus the computed ideal release date for 2.0.17 would be 2020-08-20, which is 
in three weeks or less.

The current list of patches in the queue is:
 - 2.0, 2.1                  - MAJOR   : dns: Make the do-resolve action 
thread-safe
 - 2.1                       - MEDIUM  : mux-h1: Subscribe rather than waking 
up in h1_rcv_buf()
 - 2.0                       - MEDIUM  : mux-h2: Emit an error if the response 
chunk formatting is incomplete
 - 2.0, 2.1                  - MEDIUM  : resolve: fix init resolving for ring 
and peers section.
 - 2.1                       - MEDIUM  : server: resolve state file handle leak 
on reload
 - 2.1                       - MEDIUM  : mux-h1: Disable splicing for the 
conn-stream if read0 is received
 - 2.1                       - MEDIUM  : mux-h1: Continue to process request 
when switching in tunnel mode
 - 2.1                       - MEDIUM  : channel: Be aware of SHUTW_NOW flag 
when output data are peeked
 - 2.0, 2.1                  - MEDIUM  : mux-h1: Disable the splicing when 
nothing is received
 - 2.1                       - MEDIUM  : pattern: Add a trailing \0 to match 
strings only if possible
 - 2.1                       - MEDIUM  : ebtree: use a byte-per-byte memcmp() 
to compare memory blocks
 - 2.0, 2.1                  - MEDIUM  : dns: Release answer items when a DNS 
resolution is freed
 - 2.1                       - MEDIUM  : fcgi-app: fix memory leak in 
fcgi_flt_http_headers
 - 2.1                       - MEDIUM  : server: fix possibly uninitialized 
state file on close
 - 2.1                       - MEDIUM  : connection: Continue to recv data to a 
pipe when the FD is not ready
 - 2.1                       - MEDIUM  : lists: add missing store barrier on 
MT_LIST_BEHEAD()
 - 2.0, 2.1                  - MEDIUM  : mux-h1: Wakeup the H1C in h1_rcv_buf() 
if more data are expected
 - 2.1                       - MEDIUM  : pattern: fix thread safety of pattern 
matching
 - 2.1                       - MEDIUM  : ssl: crt-list must continue parsing on 
ERR_WARN
 - 2.1                       - MEDIUM  : fetch: Fix hdr_ip misparsing IPv4 
addresses due to missing NUL
 - 2.1                       - MEDIUM  : log: don't hold the log lock during 
writev() on a file descriptor
 - 2.1                       - MEDIUM  : lists: add missing store barrier in 
MT_LIST_ADD/MT_LIST_ADDQ
 - 2.1                       - MEDIUM  : log: issue mixing sampled to not 
sampled log servers.
 - 2.1, 2.2                  - MINOR   : mux-fcgi: Don't url-decode the 
QUERY_STRING parameter anymore
 - 2.1                       - MINOR   : http: make smp_fetch_body() report 
that the contents may change
 - 2.1                       - MINOR   : http_ana: clarify connection pointer 
check on L7 retry
 - 2.1                       - MINOR   : mworker/cli: fix semicolon escaping in 
master CLI
 - 2.1                       - MINOR   : ssl: fix ssl-{min,max}-ver with 
openssl < 1.1.0
 - 2.1                       - MINOR   : mux-h1: Disable splicing only if input 
data was processed
 - 2.1                       - MINOR   : cli: allow space escaping on the CLI
 - 2.1                       - MINOR   : http_act: don't check capture id in 
backend (2)
 - 2.1                       - MINOR   : spoe: add missing key length check 
before checking key names
 - 2.1                       - MINOR   : spoe: correction of setting bits for 
analyzer
 - 2.1                       - MINOR   : systemd: Wait for network to be online
 - 2.1                       - MINOR   : proxy: always initialize the trash in 
show servers state
 - 2.1                       - MINOR   : proxy: fix dump_server_state()'s 
misuse of the trash
 - 2.1                       - MINOR   : mux-h1: Fix the splicing in TUNNEL mode
 - 2.0, 2.1, 2.2             - MINOR   : debug: Don't dump the lua stack if it 
is not initialized
 - 2.0, 2.1                  - MINOR   : cfgparse: don't increment linenum on 
incomplete lines
 - 2.1                       - MINOR   : sample: Free str.area in 
smp_check_const_bool
 - 2.1                       - MINOR   : mux-h1: Don't read data from a pipe if 
the mux is unable to receive
 - 2.1                       - MINOR   : mworker/cli: fix the escaping in the 
master CLI
 - 2.1                       - MINOR   : mux-fcgi: Set conn state to RECORD_P 
when skipping the record padding
 - 2.1                       - MINOR   : backend: Remove CO_FL_SESS_IDLE if a 
client remains on the last server
 - 2.1                       - MINOR   : sample: Free str.area in 
smp_check_const_meth
 - 2.1                       - MINOR   : mux-fcgi: Set flags on the right 
stream field for empty FCGI_STDOUT
 - 2.0, 2.1                  - MINOR   : threads: Don't forget to init each 
thread toremove_lock.
 - 2.1                       - MINOR   : mux-fcgi: Handle empty STDERR record
 - 2.1                       - MINOR   : tcp-rules: tcp-response must check the 
buffer's fullness

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