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.4.4 was issued on 2021-09-07. There are currently 15
patches in the queue cut down this way:
- 1 MAJOR, first one merged on 2021-09-20
- 3 MEDIUM, first one merged on 2021-09-10
- 11 MINOR, first one merged on 2021-09-08
Thus the computed ideal release date for 2.4.5 would be 2021-10-04, which is in
two weeks or less.
Last release 2.3.14 was issued on 2021-09-07. There are currently 11
patches in the queue cut down this way:
- 2 MEDIUM, first one merged on 2021-09-20
- 9 MINOR, first one merged on 2021-09-20
Thus the computed ideal release date for 2.3.15 would be 2021-10-18, which is
in four weeks or less.
Last release 2.2.17 was issued on 2021-09-07. There are currently 5
patches in the queue cut down this way:
- 1 MEDIUM, first one merged on 2021-09-20
- 4 MINOR, first one merged on 2021-09-20
Thus the computed ideal release date for 2.2.18 would be 2021-11-15, which is
in eight weeks or less.
Last release 2.0.25 was issued on 2021-09-07. There are currently 5
patches in the queue cut down this way:
- 1 MEDIUM, first one merged on 2021-09-20
- 4 MINOR, first one merged on 2021-09-20
Thus the computed ideal release date for 2.0.26 would be 2021-12-13, which is
in twelve weeks or less.
The current list of patches in the queue is:
- 2.4 - MAJOR : mux-h1: Don't eval input data if an
error was reported
- 2.3, 2.4 - MEDIUM : http-ana: Reset channels analysers
when returning an error
- 2.4 - MEDIUM : mux-h1: Remove "Upgrade:" header for
requests with payload
- 2.2, 2.3, 2.4 - MEDIUM : stream-int: Don't block SI on a
channel policy if EOI is reached
- 2.0 - MEDIUM : http: check for a channel pending data
before waiting
- 2.0 - MINOR : stats: fix the POST requests
processing in legacy mode
- 2.4 - MINOR : flt-trace: fix an infinite loop when
random-parsing is set
- 2.4 - MINOR : connection: prevent null deref on mux
cleanup task allocation
- 2.0, 2.2, 2.3, 2.4 - MINOR : cli/payload: do not search for
args inside payload
- 2.3, 2.4 - MINOR : lua: Yield in channel functions only
if lua context can yield
- 2.3, 2.4 - MINOR : stream: Don't release a stream if
FLT_END is still registered
- 2.0, 2.2, 2.3, 2.4 - MINOR : systemd: ExecStartPre must use -Ws
- 2.3, 2.4 - MINOR : filters: Always set FLT_END analyser
when CF_FLT_ANALYZE flag is set
- 2.3, 2.4 - MINOR : lua: Don't yield in channel.append()
and channel.set()
- 2.0, 2.2, 2.3, 2.4 - MINOR : compat: make sure __WORDSIZE is
always defined
- 2.3, 2.4 - MINOR : filters: Set right FLT_END analyser
depending on channel
- 2.2, 2.3, 2.4 - MINOR : tcpcheck: Improve LDAP response
parsing to fix LDAP check
--
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.
