Re: travis-ci: should we drop openssl-1.1.0 and replace it with 3.0 ?
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 > openssl development code at one point in time. This actually is a pretty valid point I hadn't thought about and which we experienced already in the past. It's not rare that a change gets reverted in other projects, and wasting time working around it just to see it finally cancelled is not cool. With all this said, I tend to see the CI as a way to lower the number of surprizes. This means that the most relevant stuff to test there is what we can reasonably expect to encounter in field. If some mainstream distros ship with specific openssl versions and they take care of the support themselves, it seems reasonable to keep these versions. That does not mean we have to test all combinations, as we can reasonably expect that testing a wide enough spectrum increases the likelihood that what is located between both extremities will also work. So if 1.1.0 is still shipped and maintained in relevant distros, we can keep it. Just my two cents, Willy
Re: travis-ci: should we drop openssl-1.1.0 and replace it with 3.0 ?
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 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 openssl development code at one point in time. Lukas
Re: travis-ci: should we drop openssl-1.1.0 and replace it with 3.0 ?
yep, 3.0 stands for openssl master branch. the point is to catch incompatibilities before it is released. вт, 19 нояб. 2019 г. в 22:51, Gibson, Brian (IMS) : > Maybe after they stop security fixes we can drop 1.1.0. I know there are > many distributions still in support that use this branch. 3.0 doesn’t > exist yet, and won’t until later in 2020 which is unfortunate since that > means there will be no FIPS validated branch for several months. > > > > *From:* Илья Шипицин [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 нояб. 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 support on 11th September 2019" > > > > > > what if we drop it ? and replace with 3.0 ? > > > > cheers, > > Ilya Shipitcin > > > -- > > Information in this e-mail may be confidential. It is intended only for > the addressee(s) identified above. If you are not the addressee(s), or an > employee or agent of the addressee(s), please note that any dissemination, > distribution, or copying of this communication is strictly prohibited. If > you have received this e-mail in error, please notify the sender of the > error. >
RE: travis-ci: should we drop openssl-1.1.0 and replace it with 3.0 ?
Maybe after they stop security fixes we can drop 1.1.0. I know there are many distributions still in support that use this branch. 3.0 doesn’t exist yet, and won’t until later in 2020 which is unfortunate since that means there will be no FIPS validated branch for several months. From: Илья Шипицин [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 нояб. 2019 г. в 22:41, Илья Шипицин mailto:chipits...@gmail.com>>: 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 Information in this e-mail may be confidential. It is intended only for the addressee(s) identified above. If you are not the addressee(s), or an employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error.
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, Илья Шипицин : > 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 >
travis-ci: should we drop openssl-1.1.0 and replace it with 3.0 ?
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