Christopher, Am 17.07.20 um 17:19 schrieb Christopher Faulet: > Le 17/07/2020 à 16:58, Tim Düsterhus a écrit : >> Christopher, >> >> Am 17.07.20 um 16:34 schrieb Christopher Faulet: >>> HAProxy 2.0.16 was released on 2020/07/17. It added 45 new commits >>> after version >>> 2.0.15. >> >> I'm a bit surprised seeing a new 2.0 before a new 2.1 / 2.2. Will they >> also come today? I'm especially interested in 2.1.8 because of this >> patch: >> http://git.haproxy.org/?p=haproxy-2.1.git;a=commit;h=4cbc30d405b06e7ff1ba6a6f3be58af786af81bc >> >> >> While I deployed a custom built 2.2 today for #758 I don't want to do >> this on all machines due to the increased operational effort. >> >> Also releasing a new 2.0 before the newer branches violates the contract >> that upgrading HAProxy to a newer branch will never reintroduce fixed >> bugs. I believe I read this contract somewhere in the past, but I can't >> find it right now. >> > > I released the 2.0.16 in first because of a major bug on the 2.0.15 > about random backend connections on connection retry. So, I guess we may
Yes, I understand that 2.0.16 was a very important release for users of 2.0.x. > emit a 2.1 too. There are some annoying medium bugs and the 2.1.7 is 1.5 > month old. For the 2.2, there are still pending bugs we should fix > before emitting a new release. At least the issue #758 as you said, but > also the #756. > I found the "contract" I was referring to: https://github.com/haproxy/haproxy/blob/a267b5df4a20016a7daee5f457b219c1a2c48f39/BRANCHES#L98-L108 I quote, highlighting mine: > The fix will be backported into 1.9 and from there into 1.8. 1.9.5 **will be issued with the fix before** 1.8.19 will be issued. This guarantees that for any version 1.8 having the fix, there always exists a version 1.9 with it as well. I understand that releasing a new version takes time to write the announcement and stuff and I also understand that 2.0 had priority. But I don't think that excuses violating one's own rules that exist for good reason. Users upgrading from 2.0.16 to 2.2.0 will now see bugs that have already been fixed in 2.0.16, but not 2.2.0. Best regards Tim Düsterhus
