Re: [ANNOUNCE] haproxy-2.5.0

2021-12-14 Thread William Lallemand
On Tue, Nov 23, 2021 at 05:18:37PM +0100, Willy Tarreau wrote: > > Hi, > > HAProxy 2.5.0 was released on 2021/11/23. It added 9 new commits after > version 2.5-dev15, fixing minor last-minute details (bind warnings > that turned to errors, and an incorrect free in the backend SSL cache). > Hi Th

Re: [ANNOUNCE] haproxy-2.5.0

2021-12-08 Thread Lukas Tribus
Hello Cyril, On Tue, 23 Nov 2021 at 17:18, Willy Tarreau wrote: > > Hi, > > HAProxy 2.5.0 was released on 2021/11/23. It added 9 new commits after > version 2.5-dev15, fixing minor last-minute details (bind warnings > that turned to errors, and an incorrect free in the backend SSL cache). could

Re: [ANNOUNCE] haproxy-2.5.0

2021-11-23 Thread Илья Шипицин
вт, 23 нояб. 2021 г. в 21:45, Willy Tarreau : > On Tue, Nov 23, 2021 at 05:40:22PM +0100, Tim Düsterhus wrote: > > Willy, > > > > On 11/23/21 5:18 PM, Willy Tarreau wrote: > > > As a reminder, this is a stable version which will receive fixes for > > > around 12 months. Its initially scheduled EOL

Re: [ANNOUNCE] haproxy-2.5.0

2021-11-23 Thread Willy Tarreau
On Tue, Nov 23, 2021 at 05:40:22PM +0100, Tim Düsterhus wrote: > Willy, > > On 11/23/21 5:18 PM, Willy Tarreau wrote: > > As a reminder, this is a stable version which will receive fixes for > > around 12 months. Its initially scheduled EOL is 2023-Q1 but it can be > > slightly extended depending

Re: [ANNOUNCE] haproxy-2.5.0

2021-11-23 Thread Tim Düsterhus
Willy, On 11/23/21 5:18 PM, Willy Tarreau wrote: As a reminder, this is a stable version which will receive fixes for around 12 months. Its initially scheduled EOL is 2023-Q1 but it can be slightly extended depending on adoption and feedback. You're living in the future. haproxy.org shows 2022

[ANNOUNCE] haproxy-2.5.0

2021-11-23 Thread Willy Tarreau
Hi, HAProxy 2.5.0 was released on 2021/11/23. It added 9 new commits after version 2.5-dev15, fixing minor last-minute details (bind warnings that turned to errors, and an incorrect free in the backend SSL cache). We were slightly delayed compared to my initial expectations (~1-2 weeks), but noth