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.3.10 was issued on 2021-04-23.  There are currently 10 
patches in the queue cut down this way:
    - 7 MEDIUM, first one merged on 2021-04-28
    - 3 MINOR, first one merged on 2021-04-28

Thus the computed ideal release date for 2.3.11 would be 2021-05-26, which is 
in three weeks or less.

    Last release 2.1.12 was issued on 2021-03-18.  There are currently 44 
patches in the queue cut down this way:
    - 1 BUG, first one merged on 2021-04-29
    - 3 MAJOR, first one merged on 2021-04-09
    - 22 MEDIUM, first one merged on 2021-03-31
    - 18 MINOR, first one merged on 2021-03-31

Thus the computed ideal release date for 2.1.13 would be 2021-05-07, which is 
in one week or less.

    Last release 2.0.22 was issued on 2021-04-12.  There are currently 26 
patches in the queue cut down this way:
    - 1 MAJOR, first one merged on 2021-04-29
    - 14 MEDIUM, first one merged on 2021-04-29
    - 11 MINOR, first one merged on 2021-04-29

Thus the computed ideal release date for 2.0.23 would be 2021-05-27, which is 
in three weeks or less.

The current list of patches in the queue is:
 - 2.1                       - BUG     : mworker/cli: do not use the unix_bind 
prefix for the master CLI socket
 - 2.1                       - MAJOR   : dns: fix null pointer dereference in 
snr_update_srv_status
 - 2.1                       - MAJOR   : dns: disabled servers through SRV 
records never recover
 - 2.0, 2.1                  - MAJOR   : mux-h2: Properly detect too large 
frames when decoding headers
 - 2.0, 2.1, 2.3             - MEDIUM  : peers: reset tables stage flags stages 
on new conns
 - 2.0, 2.1                  - MEDIUM  : threads: Ignore current thread to end 
its harmless period
 - 2.0, 2.1                  - MEDIUM  : sample: Fix adjusting size in field 
converter
 - 2.0, 2.1, 2.3             - MEDIUM  : peers: register last acked value as 
origin receiving a resync req
 - 2.0, 2.1                  - MEDIUM  : mux-h2: Properly handle shutdowns when 
received with data
 - 2.0, 2.1                  - MEDIUM  : mux-h2: Fix dfl calculation when 
merging CONTINUATION frames
 - 2.1                       - MEDIUM  : freq_ctr/threads: use the 
global_now_ms variable
 - 2.0, 2.1, 2.3             - MEDIUM  : peers: reset commitupdate value in new 
conns
 - 2.1                       - MEDIUM  : debug/lua: Use internal hlua function 
to dump the lua traceback
 - 2.0, 2.1, 2.3             - MEDIUM  : peers: initialize resync timer to get 
an initial full resync
 - 2.0, 2.1                  - MEDIUM  : config: fix cpu-map notation with both 
process and threads
 - 2.0, 2.1, 2.3             - MEDIUM  : peers: re-work updates lookup during 
the sync on the fly
 - 2.1                       - MEDIUM  : resolvers: Don't release resolution 
from a requester callbacks
 - 2.1                       - MEDIUM  : lua: Always init the lua stack before 
referencing the context
 - 2.1                       - MEDIUM  : mux-h1: make h1_shutw_conn() idempotent
 - 2.1                       - MEDIUM  : time: make sure to always initialize 
the global tick
 - 2.0, 2.1                  - MEDIUM  : peers: re-work connection to new 
process during reload.
 - 2.0, 2.1, 2.3             - MEDIUM  : peers: stop considering ack messages 
teaching a full resync
 - 2.0, 2.1                  - MEDIUM  : peers: re-work refcnt on table to 
protect against flush
 - 2.1                       - MEDIUM  : task: close a possible data race 
condition on a tasklet's list link
 - 2.1                       - MEDIUM  : thread: Fix a deadlock if an isolated 
thread is marked as harmless
 - 2.0, 2.1, 2.3             - MEDIUM  : peers: reset starting point if peers 
appears longly disconnected
 - 2.0, 2.1                  - MINOR   : mworker: don't use oldpids[] anymore 
for reload
 - 2.1, 2.3                  - MINOR   : mux-fcgi: Don't send normalized uri to 
FCGI application
 - 2.0, 2.1                  - MINOR   : http_htx: Remove BUG_ON() from 
http_get_stline() function
 - 2.1                       - MINOR   : connection: Fix fc_http_major and 
bc_http_major for TCP connections
 - 2.0, 2.1, 2.3             - MINOR   : applet: Notify the other side if data 
were consumed by an applet
 - 2.0, 2.1                  - MINOR   : mworker/init: don't reset nb_oldpids 
in non-mworker cases
 - 2.0, 2.1                  - MINOR   : peers: remove useless table check if 
initial resync is finished
 - 2.1                       - MINOR   : stats: Apply proper styles in HTML 
status page.
 - 2.0, 2.1                  - MINOR   : http-fetch: Make method smp safe if 
headers were already forwarded
 - 2.1                       - MINOR   : tcp: fix silent-drop workaround for 
IPv6
 - 2.0, 2.1                  - MINOR   : logs: Report the true number of 
retries if there was no connection
 - 2.0, 2.1                  - MINOR   : mux-h1: Release idle server H1 
connection if data are received
 - 2.1                       - MINOR   : http_fetch: make hdr_ip() reject 
trailing characters
 - 2.0, 2.1                  - MINOR   : tools: fix parsing "us" unit for timers
 - 2.1                       - MINOR   : http_fetch: make hdr_ip() resistant to 
empty fields
 - 2.0, 2.1                  - MINOR   : server: free srv.lb_nodes in 
free_server
 - 2.1                       - MINOR   : resolvers: Unlink DNS resolution to 
set RMAINT on SRV resolution
 - 2.0, 2.1, 2.3             - MINOR   : htx: Preserve HTX flags when draining 
data from an HTX message

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