On Sun, May 05, 2019 at 07:07:21AM +0200, Willy Tarreau wrote:
> Thus I conclude that it crashed, and that all other threads just met at
> the same lock while the core was being dumped in this one.
Or maybe the tree got corrupted and __eb_insert_dup() entered an endless
loop. If that's the case
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
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
On Sat, May 4, 2019 at 1:58 PM Vincent Bernat wrote:
> The more changes, the less likely the release team will accept the
> change. Assuming we can only make one proposition (which is not true),
> what would you (as upstream) try? 1.8.19, one bug, all major bugs, even
> more bugs, or 1.8.20?
Not
Vincent,
Am 04.05.19 um 13:57 schrieb Vincent Bernat:
> The more changes, the less likely the release team will accept the
> change. Assuming we can only make one proposition (which is not true),
> what would you (as upstream) try? 1.8.19, one bug, all major bugs, even
> more bugs, or 1.8.20?
>
❦ 29 avril 2019 11:04 +02, Christopher Faulet :
> HAProxy 1.8.20 was released on 2019/04/25. It added 48 new commits
> after version 1.8.19.
Hey!
Debian Buster will soon be released (nobody knows exactly when, but we
are in full freeze since 2 months). It currently contains HAProxy
1.8.19. I
6 matches
Mail list logo
