On Tue, Nov 19, 2019 at 11:57:56PM +0100, Lukas Tribus wrote:
> Testing and implementing build fixes for APIs while they are under active
> development not only takes away precious dev time, it's also causes our own
> code to be messed up with workarounds possibly only needed for specific
>
Hello,
On Tuesday, 19 November 2019, Илья Шипицин wrote:
> yep, 3.0 stands for openssl master branch.
> the point is to catch incompatibilities before it is released.
>
I am objecting to this. This can be done WHEN openssl declares that the API
is stable.
Testing and implementing build fixes
Proxy
> *Subject:* Re: travis-ci: should we drop openssl-1.1.0 and replace it
> with 3.0 ?
>
>
>
> well, we can actually build bigger matrix by adding builds. I just want to
> save some electricity on non needed builds.
>
>
>
> вт, 19 нояб. 2019 г. в 22:41, Илья Ши
Шипицин [mailto:chipits...@gmail.com]
Sent: Tuesday, November 19, 2019 12:48 PM
To: HAProxy
Subject: Re: travis-ci: should we drop openssl-1.1.0 and replace it with 3.0 ?
well, we can actually build bigger matrix by adding builds. I just want to save
some electricity on non needed builds.
вт, 19
well, we can actually build bigger matrix by adding builds. I just want to
save some electricity on non needed builds.
вт, 19 нояб. 2019 г. в 22:41, Илья Шипицин :
> hello,
>
> https://www.openssl.org/source/ says "The 1.1.0 series is currently only
> receiving security fixes and will go out of
hello,
https://www.openssl.org/source/ says "The 1.1.0 series is currently only
receiving security fixes and will go out of support on 11th September 2019"
what if we drop it ? and replace with 3.0 ?
cheers,
Ilya Shipitcin
6 matches
Mail list logo
