stable-bot: Bugfixes waiting for a release 2.1 (4)
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.7 was issued on 2020-06-09. There are currently 4 patches in
the queue cut down this way:
- 3 MEDIUM, first one merged on 2020-06-12
- 1 MINOR, first one merged on 2020-06-12
Thus the computed ideal release date for 2.1.8 would be 2020-07-10, which is in
two weeks or less.
The current list of patches in the queue is:
- 2.1 - MEDIUM : log: don't hold the log lock during
writev() on a file descriptor
- 2.1 - MEDIUM : ssl: crt-list must continue parsing on
ERR_WARN
- 2.1 - MEDIUM : pattern: fix thread safety of pattern
matching
- 2.1 - MINOR : ssl: fix ssl-{min,max}-ver with
openssl < 1.1.0
--
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.
stable-bot: Bugfixes waiting for a release 2.1 (4)
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.7 was issued on 2020-06-09. There are currently 4 patches in
the queue cut down this way:
- 3 MEDIUM, first one merged on 2020-06-12
- 1 MINOR, first one merged on 2020-06-12
Thus the computed ideal release date for 2.1.8 would be 2020-07-10, which is in
three weeks or less.
The current list of patches in the queue is:
- 2.1 - MEDIUM : pattern: fix thread safety of pattern
matching
- 2.1 - MEDIUM : log: don't hold the log lock during
writev() on a file descriptor
- 2.1 - MEDIUM : ssl: crt-list must continue parsing on
ERR_WARN
- 2.1 - MINOR : ssl: fix ssl-{min,max}-ver with
openssl < 1.1.0
--
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.
stable-bot: Bugfixes waiting for a release 2.1 (4)
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.7 was issued on 2020-06-09. There are currently 4 patches in
the queue cut down this way:
- 3 MEDIUM, first one merged on 2020-06-12
- 1 MINOR, first one merged on 2020-06-12
Thus the computed ideal release date for 2.1.8 would be 2020-07-10, which is in
four weeks or less.
The current list of patches in the queue is:
- 2.1 - MEDIUM : ssl: crt-list must continue parsing on
ERR_WARN
- 2.1 - MEDIUM : log: don't hold the log lock during
writev() on a file descriptor
- 2.1 - MEDIUM : pattern: fix thread safety of pattern
matching
- 2.1 - MINOR : ssl: fix ssl-{min,max}-ver with
openssl < 1.1.0
--
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.
stable-bot: Bugfixes waiting for a release 2.1 (4), 2.0 (1)
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 4 patches in the queue cut down this way: - 4 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 within the last week. Last release 2.0.14 was issued on 2020-04-02. There are currently 1 patches in the queue cut down this way: - 1 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 within the last week. The current list of patches in the queue is: - 2.0, 2.1 - MINOR : protocol_buffer: Wrong maximum shifting. - 2.1 - MINOR : ssl: memleak of the struct cert_key_and_chain - 2.1 - MINOR : ssl/cli: memory leak in 'set ssl cert' - 2.1 - MINOR : connection: always send address-less LOCAL PROXY connections -- 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.
stable-bot: Bugfixes waiting for a release 2.1 (4), 2.0 (1)
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 4 patches in the queue cut down this way: - 4 MINOR, first one merged on 2020-04-02 Thus the computed ideal release date for 2.1.5 would be 2020-04-30, which is in one week or less. Last release 2.0.14 was issued on 2020-04-02. There are currently 1 patches in the queue cut down this way: - 1 MINOR, first one merged on 2020-04-02 Thus the computed ideal release date for 2.0.15 would be 2020-04-30, which is in one week or less. The current list of patches in the queue is: - 2.1 - MINOR : connection: always send address-less LOCAL PROXY connections - 2.0, 2.1 - MINOR : protocol_buffer: Wrong maximum shifting. - 2.1 - MINOR : ssl: memleak of the struct cert_key_and_chain - 2.1 - MINOR : ssl/cli: memory leak in 'set ssl cert' -- 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.
stable-bot: Bugfixes waiting for a release 2.1 (4), 2.0 (1)
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 4 patches in the queue cut down this way: - 4 MINOR, first one merged on 2020-04-02 Thus the computed ideal release date for 2.1.5 would be 2020-04-30, which is in two weeks or less. Last release 2.0.14 was issued on 2020-04-02. There are currently 1 patches in the queue cut down this way: - 1 MINOR, first one merged on 2020-04-02 Thus the computed ideal release date for 2.0.15 would be 2020-04-30, which is in two weeks or less. The current list of patches in the queue is: - 2.0, 2.1 - MINOR : protocol_buffer: Wrong maximum shifting. - 2.1 - MINOR : connection: always send address-less LOCAL PROXY connections - 2.1 - MINOR : ssl: memleak of the struct cert_key_and_chain - 2.1 - MINOR : ssl/cli: memory leak in 'set ssl cert' -- 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.
