Hi William, On Thu, Apr 16, 2020 at 10:37:53AM +0200, William Lallemand wrote: > Also there isn't a date for each major release on the website, only the > date of the latest minor release, which is a problem to understand at > which period of the cycle the version is. So we should probably add the > date of the first release and the estimated end of life date, which help > to chose between 2 versions.
I 100% agree with this and in fact I already use the exact same table when it comes to kernel support of stable branches, so I can easily understand how everyone needs the same for haproxy. I'll do this. > Regarding the current development version, an estimated release date > could be great too, with the current phase of development. It will add > more visibility on the development cycle. It's a good idea as well, and we could mention that it's expected to become LTS and it will answer all those who were wondering the same question as Aleks'. Thanks for the suggestion! Willy
