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.2 was issued on 2020-07-31.  There are currently 16 patches in 
the queue cut down this way:
    - 1 MAJOR, first one merged on 2020-08-05
    - 4 MEDIUM, first one merged on 2020-08-05
    - 11 MINOR, first one merged on 2020-08-05

Thus the computed ideal release date for 2.2.3 would be 2020-08-19, which is in 
one week or less.

Last release 2.1.8 was issued on 2020-07-31.  There are currently 12 patches in 
the queue cut down this way:
    - 3 MEDIUM, first one merged on 2020-08-05
    - 9 MINOR, first one merged on 2020-08-11

Thus the computed ideal release date for 2.1.9 would be 2020-09-04, which is in 
four weeks or less.

Last release 2.0.17 was issued on 2020-07-31.  There are currently 7 patches in 
the queue cut down this way:
    - 3 MEDIUM, first one merged on 2020-08-05
    - 4 MINOR, first one merged on 2020-08-11

Thus the computed ideal release date for 2.0.18 would be 2020-10-04, which is 
in eight weeks or less.

Last release 1.8.26 was issued on 2020-08-03.  There are currently 6 patches in 
the queue cut down this way:
    - 2 MEDIUM, first one merged on 2020-08-05
    - 4 MINOR, first one merged on 2020-08-03

Thus the computed ideal release date for 1.8.27 would be 2020-10-26, which is 
in eleven weeks or less.

The current list of patches in the queue is:
 - 2.2                       - MAJOR   : dns: disabled servers through SRV 
records never recover
 - 1.8, 2.0, 2.1, 2.2            - MEDIUM  : map/lua: Return an error if a map 
is loaded during runtime
 - 2.0, 2.1, 2.2             - MEDIUM  : mux-h1: Refresh H1 connection timeout 
after a synchronous send
 - 2.1, 2.2                  - MEDIUM  : ssl: memory leak of ocsp data at 
SSL_CTX_free()
 - 2.2                       - MEDIUM  : ssl: fix the ssl-skip-self-issued-ca 
option
 - 1.8, 2.0                  - MEDIUM  : mux-h2: Don't fail if nothing is 
parsed for a legacy chunk response
 - 2.0, 2.1, 2.2             - MINOR   : snapshots: leak of snapshots on 
deinit()
 - 2.1, 2.2                  - MINOR   : lua: Duplicate map name to load it 
when a new Map object is created
 - 1.8, 2.0, 2.1, 2.2            - MINOR   : lua: Check argument type to 
convert it to IPv4/IPv6 arg validation
 - 2.1, 2.2                  - MINOR   : converters: Store the sink in an arg 
pointer for debug() converter
 - 2.2                       - MINOR   : spoa-server: fix size_t format printing
 - 1.8, 2.0, 2.1, 2.2            - MINOR   : lua: Check argument type to 
convert it to IP mask in arg validation
 - 1.8, 2.0, 2.1, 2.2            - MINOR   : stats: use strncmp() instead of 
memcmp() on health states
 - 2.1, 2.2                  - MINOR   : ssl: fix memory leak at OCSP loading
 - 2.1, 2.2                  - MINOR   : lua: Duplicate lua strings in sample 
fetches/converters arg array
 - 2.2                       - MINOR   : ssl: ssl-skip-self-issued-ca requires 
>= 1.0.2
 - 1.8                       - MINOR   : dns: ignore trailing dot
 - 2.1, 2.2                  - MINOR   : arg: Fix leaks during arguments 
validation for fetches/converters

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