iperf3 3.17 versioning problem

[bmah888]

Somehow in the iperf 3.17 source tarball, the version number of the binary built seems to still be 3.16+. It should read 3.17. Also the version number in configure.ac on master now reads 3.17+. Did bootstrap.sh correct regenerate the configuration files?

We might need to roll a new 3.17.1 to get the tarball and the program to have the same version.

We should run through the steps in the release engineering checklist to see if there's some incorrect assumptions or something I didn't write down correctly.

[ar51an]

I was about to open this issue. It is in configure file

PACKAGE_VERSION='3.16+'
PACKAGE_STRING='iperf 3.16+'

[bmah888]

Fixed in 3.17.1.