❦ 29 avril 2019 11:04 +02, Christopher Faulet <[email protected]>:

> 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 don't think it would be possible to push 1.8.20 as is.

We can either keep 1.8.19 as is or select a few critical patches to
apply on it. For example, we could take the MAJOR patches:

    BUG/MAJOR: checks: segfault during tcpcheck_main
    BUG/MAJOR: http_fetch: Get the channel depending on the keyword used
    BUG/MAJOR: listener: Make sure the listener exist before using it.
    BUG/MAJOR: spoe: Fix initialization of thread-dependent fields
    BUG/MAJOR: stats: Fix how huge POST data are read from the channel

And maybe:

    BUG/MEDIUM: listener: make sure the listener never accepts too many conns

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?
-- 
Choose a data representation that makes the program simple.
            - The Elements of Programming Style (Kernighan & Plauger)

Reply via email to