вт, 18 окт. 2022 г. в 14:46, William Lallemand <[email protected]>:
> On Thu, Oct 13, 2022 at 08:54:38AM +0200, Willy Tarreau wrote: > > Hi Ilya, > > > > On Tue, Oct 11, 2022 at 12:18:40PM +0500, ???? ??????? wrote: > > > split patches attached. > > > > Sorry for the delay. Both applied now, thank you! > > Willy > > > > Hello, > > Sorry I didn't see the first commit that introduced this behavior. I'm > not sure we would want to replace the version automatically in the CI > for OpenSSL. > it was supposed behaviour for OPENSSL_VERSION=latest > > Currently we are testing the stock OpenSSL of the ubuntu which is 1.1.1, > the 1.0.2u and the "latest". The latest is currently a 3.0.x but once > the 3.1.x is released we would still need the 3.0 branch. > I think we should review our approach to "stock" and "latest" when ubuntu-latest will be 22.04 (it is shipped with 3.0.X) I'll have a look at your point as well > > I think we need something to test the latest release of a branch, and > not the latest version of all branches. Maybe we could specify "3.0.x" > to get the latest 3.0? > maybe-maybe-maybe. we can introduce "latest in 3.0.x" I guess. not much to code. > > Regards, > > -- > William Lallemand >
