Re: stable-bot: Bugfixes waiting for a release 2.2 (11), 2.1 (36), 2.0 (26), 1.8 (12)

2020-09-29 Thread Willy Tarreau
On Wed, Sep 30, 2020 at 12:00:08AM +, stable-...@haproxy.com wrote:
> Thus the computed ideal release date for 2.2.4 would be 2020-10-11, which is 
> in two weeks or less.
> Thus the computed ideal release date for 2.1.9 would be 2020-09-04, which was 
> three weeks ago.
> Thus the computed ideal release date for 2.0.18 would be 2020-10-04, which is 
> in one week or less.

If not disturbed today, I'll try to emit a bunch of versions to flush the
pipe from known bugs.

Willy



stable-bot: Bugfixes waiting for a release 2.2 (11), 2.1 (36), 2.0 (26), 1.8 (12)

2020-09-29 Thread stable-bot
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.3 was issued on 2020-09-08.  There are currently 11 patches in 
the queue cut down this way:
- 3 MEDIUM, first one merged on 2020-09-11
- 8 MINOR, first one merged on 2020-09-22

Thus the computed ideal release date for 2.2.4 would be 2020-10-11, which is in 
two weeks or less.

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

Thus the computed ideal release date for 2.1.9 would be 2020-09-04, which was 
three weeks ago.

Last release 2.0.17 was issued on 2020-07-31.  There are currently 26 patches 
in the queue cut down this way:
- 1 MAJOR, first one merged on 2020-09-07
- 11 MEDIUM, first one merged on 2020-08-05
- 14 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 one week or less.

Last release 1.8.26 was issued on 2020-08-03.  There are currently 12 patches 
in the queue cut down this way:
- 5 MEDIUM, first one merged on 2020-08-05
- 7 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 four weeks or less.

The current list of patches in the queue is:
 - 2.0, 2.1  - MAJOR   : contrib/spoa-server: Fix unhandled 
python call leading to memory leak
 - 2.0, 2.1  - MEDIUM  : mux-h1: Refresh H1 connection timeout 
after a synchronous send
 - 2.0, 2.1  - MEDIUM  : htx: smp_prefetch_htx() must always 
validate the direction
 - 2.0, 2.1  - MEDIUM  : ssl: does not look for all SNIs before 
chosing a certificate
 - 2.1, 2.2  - MEDIUM  : h2: report frame bits only for handled 
types
 - 2.0, 2.1  - MEDIUM  : http-ana: Don't wait to send 1xx 
responses received from servers
 - 2.1   - MEDIUM  : ssl: memory leak of ocsp data at 
SSL_CTX_free()
 - 2.0, 2.1  - MEDIUM  : contrib/spoa-server: Fix ipv4_address 
used instead of ipv6_address
 - 2.0, 2.1  - MEDIUM  : mux-h1: always apply the timeout on 
half-closed connections
 - 2.2   - MEDIUM  : ssl: Don't call ssl_sock_io_cb() 
directly.
 - 1.8   - MEDIUM  : pattern: fix memory leak in regex 
pattern functions
 - 1.8, 2.0, 2.1, 2.2- MEDIUM  : pattern: Renew the pattern 
expression revision when it is pruned
 - 1.8, 2.0  - MEDIUM  : mux-h2: Don't fail if nothing is 
parsed for a legacy chunk response
 - 1.8, 2.0, 2.1 - MEDIUM  : ssl: check OCSP calloc in 
ssl_sock_load_ocsp()
 - 1.8, 2.0, 2.1 - MEDIUM  : map/lua: Return an error if a map is 
loaded during runtime
 - 2.0, 2.1  - MEDIUM  : doc: Fix replace-path action 
description
 - 1.8, 2.0, 2.1 - MINOR   : reload: do not fail when no socket is 
sent
 - 2.0, 2.1  - MINOR   : contrib/spoa-server: Updating 
references to free in case of failure
 - 2.1   - MINOR   : arg: Fix leaks during arguments 
validation for fetches/converters
 - 2.0, 2.1, 2.2 - MINOR   : http-fetch: Don't set the sample type 
during the htx prefetch
 - 2.2   - MINOR   : config: Fix memory leak on config 
parse listen
 - 2.1, 2.2  - MINOR   : h2/trace: do not display "stream 
error" after a frame ACK
 - 2.0, 2.1, 2.2 - MINOR   : ssl: verifyhost is case sensitive
 - 2.0, 2.1  - MINOR   : snapshots: leak of snapshots on 
deinit()
 - 2.2   - MINOR   : Fix type passed of sizeof() for 
calloc()
 - 2.0, 2.1  - MINOR   : contrib/spoa-server: Ensure ip address 
references are freed
 - 1.8, 2.0, 2.1 - MINOR   : startup: haproxy -s cause 100% cpu
 - 1.8, 2.0, 2.1 - MINOR   : stats: use strncmp() instead of 
memcmp() on health states
 - 1.8, 2.0, 2.1 - MINOR   : lua: Check argument type to convert it 
to IPv4/IPv6 arg validation
 - 2.1   - MINOR   : http-rules: Replace path and 
query-string in "replace-path" action"
 - 2.0, 2.1, 2.2 - MINOR   : server: report correct error message 
for invalid port on "socks4"
 - 2.1   - MINOR   : ssl: fix memory leak at OCSP loading
 - 2.1   - MINOR   : lua: Duplicate lua strings in sample 
fetches/converters arg array
 - 1.8, 2.0, 2.1 - MINOR   : threads: work around a libgcc_s