Hi Tim, On Thu, Apr 24, 2025 at 12:10:58PM +0200, Tim Düsterhus wrote: > Hi > > On 4/23/25 11:51, Willy Tarreau wrote: > > Let me insist again that this version now reached end of life, so in > > theory it should not be deployed, or only as a temporary solution to help > > with a transition to a newer one. If you're still on 2.2 and don't know > > what version to choose, first, skip 2.4 which dies next year. If you want > > something super stable, 2.6 is a good one. For more responsiveness from > > developers and the community in general, better pick 3.0 or above. Note > > that counter-intuitively, the reliabilty of 3.x could actually surpass > > that of older versions thanks to a cleaner architecture and better > > troubleshooting tools in general. Now's time to say good bye to 2.2. > > HAProxy 2.2 is not yet marked EOL in the version table on haproxy.org and on > https://docs.haproxy.org/.
Yes I know, I thought about doing that at the same moment I'll update the 3.2 release. It's always a pain. > Is 2.2.34 definitely the last version for sure? > In that case, I would already remove it from > https://github.com/docker-library/haproxy. If there might be a small chance > for another release, I'll wait :-) I'm not seeing any emergency for killing it. Let's say we can wait for 3.2 to be released so that we continue to have our 5 LTS. If in the mean time someone finds a big oddity, I'm not against emitting another one. Cheers, Willy
