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.10 was issued on 2020-11-05. There are currently 12
patches in the queue cut down this way:
- 2 MAJOR, first one merged on 2020-11-13
- 2 MEDIUM, first one merged on 2020-11-13
- 8 MINOR, first one merged on 2020-11-06
Thus the computed ideal release date for 2.1.11 would be 2020-12-11, which is
in two weeks or less.
Last release 2.0.19 was issued on 2020-11-06. There are currently 11
patches in the queue cut down this way:
- 2 MAJOR, first one merged on 2020-11-13
- 2 MEDIUM, first one merged on 2020-11-13
- 7 MINOR, first one merged on 2020-11-13
Thus the computed ideal release date for 2.0.20 would be 2020-12-11, which is
in two weeks or less.
The current list of patches in the queue is:
- 2.0, 2.1 - MAJOR : spoe: Be sure to remove all references
on a released spoe applet
- 2.0, 2.1 - MAJOR : filters: Always keep all offsets up to
date during data filtering
- 2.0, 2.1 - MEDIUM : peers: fix decoding of multi-byte
length in stick-table messages
- 2.0, 2.1 - MEDIUM : filters: Forward all filtered data at
the end of http filtering
- 2.0, 2.1 - MINOR : http-fetch: Extract cookie value even
when no cookie name
- 2.0, 2.1 - MINOR : lua: set buffer size during map lookups
- 2.1 - MINOR : http-htx: Just warn if payload of an
errorfile doesn't match the C-L
- 2.0, 2.1 - MINOR : http-fetch: Fix calls w/o parentheses
of the cookie sample fetches
- 2.0, 2.1 - MINOR : peers: Do not ignore a protocol error
for dictionary entries.
- 2.0, 2.1 - MINOR : pattern: a sample marked as const
could be written
- 2.0, 2.1 - MINOR : peers: Missing TX cache entries reset.
- 2.0, 2.1 - MINOR : http-ana: Don't wait for the body of
CONNECT requests
--
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.
