On 05/01/2018 09:26 AM, Norman Branitsky wrote:
We opened a ticket with RHEL Support to ask when they would upgrade to
at least HAProxy 1.7.
This was their reply:
Most recent comment: On 2018-05-01 10:22:28, Patil, Ravindra commented:
"Hello
The reason 1.7 (as well and 1.6 and 1.8) are not in RHEL is due to
backward compatibility. We can't simply rebase haproxy in RHEL to the
latest release -- we would break existing deployments. This is a
non-starter.
We have added haproxy 1.8 to RHSCL 3.1 which should be released soon.
But it will never been in base RHEL.
*There are no defects in 1.5. It is extremely stable. Far more stable
that 1.7 or 1.8. *
Two takeaways.
Haproxy 1.5 shows how good software can be. It's a testimony to the
writers and maintainers of haproxy, even if they currently aren't
interested in a version that old. It's still a compliment.
Second, it's a hard truth that developers need to take to heart with
regards to "change". If you force breakage, you put the burden on your
customer base. And companies don't really like paying the price for the
extra burden. Not saying that software cannot change, but perhaps we
need to open our eyes a bit to the impact (which could be millions of
dollars btw) that our changes would force.
