On 30 Jul 21:29, Lukas Tribus wrote: > Hello, > > On Thu, 30 Jul 2020 at 20:49, Valter Jansons <[email protected]> wrote: > > > > On Thu, Jul 30, 2020 at 6:44 PM Harris Kaufmann <[email protected]> > > wrote: > > > my company really needs the next 2.1 release but we want to avoid > > > deploying a custom, self compiled version. > > > > > > Is there something I can do to help with the release? I guess there > > > are no blocking issues left? > > > > For mission-critical setups you should be running the LTS release > > lines. The 2.1 release line was more of a technical preview line for > > the following 2.2 LTS release, to keep changes flowing, and you should > > not expect regular new release tags on the 2.1 line considering the > > 2.2 line has shipped. I am not involved in the release process but I > > would assume the team will push a new 2.1 tag some day however I do > > not see that being a high priority for them in any way. > > > > As a result, I would instead rephrase the question in the other > > direction: Are there any blockers for you to upgrade to 2.2? > > I'm not sure I agree. > > I would be reluctant to suggest upgrading mission-critical setups to > 2.2, it's not even a month old at this point. Unless you expect to run > into bugs and have time and resources to troubleshoot it. > > 2.1 is not a technical preview, it's a proper release train with full > support. Support for it will cease in 2021-Q1, but I don't think you > can conclude that that means it's getting less love now. > > > Lukas >
I'm with Lukas on this. 2.1 is a strong release, and we should be grateful for everyone which is using that release, as their feedback is valuable for the building the next releases of HAProxy. I am not yet confident to run 2.2 in prod yet, but I will roll out 2.2 in non-prod env soon. -- (o- Julien Pivotto //\ Open-Source Consultant V_/_ Inuits - https://www.inuits.eu
signature.asc
Description: PGP signature

