stable-bot: Bugfixes waiting for a release 2.1 (27), 2.0 (24)
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.4 was issued on 2020-04-02. There are currently 27 patches in
the queue cut down this way:
- 10 MEDIUM, first one merged on 2020-05-01
- 17 MINOR, first one merged on 2020-04-02
Thus the computed ideal release date for 2.1.5 would be 2020-04-30, which was
three weeks ago.
Last release 2.0.14 was issued on 2020-04-02. There are currently 24 patches
in the queue cut down this way:
- 12 MEDIUM, first one merged on 2020-05-07
- 12 MINOR, first one merged on 2020-04-02
Thus the computed ideal release date for 2.0.15 would be 2020-04-30, which was
three weeks ago.
The current list of patches in the queue is:
- 2.0, 2.1 - MEDIUM : server/checks: Init server check
during config validity check
- 2.0, 2.1 - MEDIUM : http: the "http_first_req" sample
fetch could crash without a steeam
- 2.0, 2.1 - MEDIUM : http: the "unique-id" sample fetch
could crash without a steeam
- 2.0, 2.1 - MEDIUM : shctx: bound the number of loops that
can happen around the lock
- 2.0, 2.1 - MEDIUM : capture: capture-req/capture-res
converters crash without a stream
- 2.0, 2.1 - MEDIUM : shctx: really check the lock's value
while waiting
- 2.0, 2.1 - MEDIUM : http-ana: Handle NTLM messages
correctly.
- 2.0, 2.1 - MEDIUM : listener: mark the thread as not stuck
inside the loop
- 2.0 - MEDIUM : backend: don't access a non-existing
mux from a previous connection
- 2.0, 2.1 - MEDIUM : sample: make the CPU and latency
sample fetches check for a stream
- 2.0 - MEDIUM : checks: Always initialize checks
before starting them
- 2.0, 2.1 - MEDIUM : capture: capture.{req,res}.* crash
without a stream
- 2.0, 2.1 - MINOR : protocol_buffer: Wrong maximum
shifting.
- 2.1 - MINOR : connection: always send address-less
LOCAL PROXY connections
- 2.0, 2.1 - MINOR : debug: properly use long long instead
of long for the thread ID
- 2.1 - MINOR : mux-fcgi: Be sure to have a connection
as session's origin to use it
- 2.0, 2.1 - MINOR : ssl: default settings for ssl server
options are not used
- 2.0, 2.1 - MINOR : tools: fix the i386 version of the
div64_32 function
- 2.0, 2.1 - MINOR : checks: chained expect will not
properly wait for enough data
- 2.0, 2.1 - MINOR : http: make url_decode() optionally
convert '+' to SP
- 2.0, 2.1 - MINOR : checks: Respect the no-check-ssl option
- 2.0, 2.1 - MINOR : checks/server: use_ssl member must be
signed
- 2.1 - MINOR : ssl/cli: memory leak in 'set ssl cert'
- 2.1 - MINOR : connection: always send address-less
LOCAL PROXY connections"
- 2.0, 2.1 - MINOR : connection: make sure to correctly tag
local PROXY connections"
- 2.0, 2.1 - MINOR : check: Update server address and port
to execute an external check
- 2.1 - MINOR : ssl: memleak of the struct
cert_key_and_chain
- 2.0, 2.1 - MINOR : obj_type: Handle stream object in
obj_base_ptr() function
- 2.0, 2.1 - MINOR : peers: Incomplete peers sections
should be validated.
--
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.
Re: stable-bot: Bugfixes waiting for a release 2.1 (27), 2.0 (24)
Hi List, Am 13.05.20 um 02:00 schrieb stable-...@haproxy.com: > Last release 2.1.4 was issued on 2020-04-02. There are currently 27 patches > in the queue cut down this way: > - 10 MEDIUM, first one merged on 2020-05-01 > - 17 MINOR, first one merged on 2020-04-02 > > Thus the computed ideal release date for 2.1.5 would be 2020-04-30, which was > two weeks ago. > > Last release 2.0.14 was issued on 2020-04-02. There are currently 24 patches > in the queue cut down this way: > - 12 MEDIUM, first one merged on 2020-05-07 > - 12 MINOR, first one merged on 2020-04-02 > > Thus the computed ideal release date for 2.0.15 would be 2020-04-30, which > was two weeks ago. Is there any date planned for 2.1.5? I'm still running 2.1.3 on one machine, because I use Dovecot. Best regards Tim Düsterhus
stable-bot: Bugfixes waiting for a release 2.1 (27), 2.0 (24)
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.4 was issued on 2020-04-02. There are currently 27 patches in
the queue cut down this way:
- 10 MEDIUM, first one merged on 2020-05-01
- 17 MINOR, first one merged on 2020-04-02
Thus the computed ideal release date for 2.1.5 would be 2020-04-30, which was
two weeks ago.
Last release 2.0.14 was issued on 2020-04-02. There are currently 24 patches
in the queue cut down this way:
- 12 MEDIUM, first one merged on 2020-05-07
- 12 MINOR, first one merged on 2020-04-02
Thus the computed ideal release date for 2.0.15 would be 2020-04-30, which was
two weeks ago.
The current list of patches in the queue is:
- 2.0 - MEDIUM : backend: don't access a non-existing
mux from a previous connection
- 2.0, 2.1 - MEDIUM : server/checks: Init server check
during config validity check
- 2.0, 2.1 - MEDIUM : http: the "unique-id" sample fetch
could crash without a steeam
- 2.0, 2.1 - MEDIUM : shctx: really check the lock's value
while waiting
- 2.0, 2.1 - MEDIUM : capture: capture.{req,res}.* crash
without a stream
- 2.0, 2.1 - MEDIUM : http-ana: Handle NTLM messages
correctly.
- 2.0, 2.1 - MEDIUM : capture: capture-req/capture-res
converters crash without a stream
- 2.0, 2.1 - MEDIUM : listener: mark the thread as not stuck
inside the loop
- 2.0, 2.1 - MEDIUM : sample: make the CPU and latency
sample fetches check for a stream
- 2.0 - MEDIUM : checks: Always initialize checks
before starting them
- 2.0, 2.1 - MEDIUM : shctx: bound the number of loops that
can happen around the lock
- 2.0, 2.1 - MEDIUM : http: the "http_first_req" sample
fetch could crash without a steeam
- 2.0, 2.1 - MINOR : checks: chained expect will not
properly wait for enough data
- 2.1 - MINOR : connection: always send address-less
LOCAL PROXY connections"
- 2.0, 2.1 - MINOR : ssl: default settings for ssl server
options are not used
- 2.0, 2.1 - MINOR : protocol_buffer: Wrong maximum
shifting.
- 2.0, 2.1 - MINOR : checks: Respect the no-check-ssl option
- 2.0, 2.1 - MINOR : http: make url_decode() optionally
convert '+' to SP
- 2.1 - MINOR : ssl: memleak of the struct
cert_key_and_chain
- 2.0, 2.1 - MINOR : checks/server: use_ssl member must be
signed
- 2.0, 2.1 - MINOR : connection: make sure to correctly tag
local PROXY connections"
- 2.0, 2.1 - MINOR : check: Update server address and port
to execute an external check
- 2.0, 2.1 - MINOR : tools: fix the i386 version of the
div64_32 function
- 2.0, 2.1 - MINOR : peers: Incomplete peers sections
should be validated.
- 2.1 - MINOR : connection: always send address-less
LOCAL PROXY connections
- 2.0, 2.1 - MINOR : obj_type: Handle stream object in
obj_base_ptr() function
- 2.1 - MINOR : mux-fcgi: Be sure to have a connection
as session's origin to use it
- 2.1 - MINOR : ssl/cli: memory leak in 'set ssl cert'
- 2.0, 2.1 - MINOR : debug: properly use long long instead
of long for the thread ID
--
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.
