NFD

Can we accelerate the retirement of 16.04 to reduce the load on maestro, which is likely causing spurious timeout failures?

Eric Newberry wrote:

Can we accelerate the retirement of 16.04 to reduce the load on maestro, which is likely causing spurious timeout failures?

The platform call on April 16, 2020 didn't raise any objections to proceeding with the retirement of 16.04.

The 16.04 agents have been removed from Jenkins and all project configurations.

Davide Pesavento wrote:

As a consequence, we can raise the minimum version of toolchain components and various other dependencies. I suggest the following:

• gcc >= 7
• clang >= 5
• boost >= 1.65.1
• openssl >= 1.1.1

Alex objected to raising the minimum requirements, as he needs to support an old version of openwrt. Therefore, while we strongly encourage users to use the above minimum versions (and Ubuntu 18.04 remains the oldest version tested in jenkins), at this time we will not take any explicit steps to break compatibility with older versions of gcc, boost, and openssl.

Alex objected to raising the minimum requirements, as he needs to support an old version of openwrt.

When I mentioned that I have OpenWrt 18.06, I'm told that I must upgrade the OS and stop buying #CrappyHardware.
When Alex wants to support OpenWrt 18.06, he can keep the version support.
Double standard.

Junxiao Shi wrote:

Alex objected to raising the minimum requirements, as he needs to support an old version of openwrt.

When I mentioned that I have OpenWrt 18.06, I'm told that I must upgrade the OS and stop buying #CrappyHardware.
When Alex wants to support OpenWrt 18.06, he can keep the version support.
Double standard.

You never voiced your concerns here on this issue, or during any recent NDN calls, or on gerrit. In fact, you were invited to review the initial version of the change that raised the minimum requirements, and not only you didn't object, but you explicitly gave it a +1.
So please refrain from making these false accusations.

I put +1 because the commit matches the task. It doesn't mean I'm not pissed.

Alex objected to raising the minimum requirements, as he needs to support an old version of openwrt.

This is getting ridiculous. I got this code review comment:

we're trying to avoid breaking compat with boost 1.58.0 so don't use data-driven tests yet please.

The OpenWrt build system does not run the unit tests, and therefore it should be perfectly fine to use Boost 1.65 features in unit testing.

Not sure why do you like commenting on old issues instead of having a normal conversation in Gerrit. You have a valid point of including the data-driven test and I have no objections. Davide's comment was a suggestion, as you could do the same without introducing dependency. But in any case, the referred "compatibility" is best effort and I would prefer having the main codebase compilable with older versions of Boost. Others may disagree, but tests for me not the main codebase, and one can take a leap of faith and compile the code without tests (or compile with some tests removed).