1Subject: iperf3 status, June 2017 2 3iperf 3.2 Release Plans 4----------------------- 5 6We've done quite a bit of work the past few weeks getting the master 7branch in shape to cut a new release, which will be the first of the 83.2.x series. These changes include fixes for a number of 9long-standing bugs (such as some of the statistics computation, and 10fixes for --file), as well as new features (for example optional 11authentication and a configurable client connection timeout) and 12general improvements (better timing for the --bitrate/--bandwidth 13options). 14 15We'd like to encourage users in the community who are comfortable 16compiling iperf3 from GitHub sources, to checkout / clone the iperf3 17master branch from GitHub and try it out in their environments. (No 18tarballs will be produced until the official 3.2 release, although I'd 19say we're basically in "release candidate" stage now.) 20 21There is a mostly-final set of release notes in the RELEASE_NOTES file 22on master, so you can see what's new, changed, fixed, and so on. 23 24Assuming no serious problems, we're aiming for an official release in 25mid- to late-June (2017!). 26 27iperf3 Support 28-------------- 29 30After a lot of issue triage, we're down to 38 issues in the issue 31tracker (plus three outstanding pull requests). As mentioned in an 32earlier update, a lot of the issues we closed were user questions, not 33bug reports or enhancement requests. We'd like to direct user 34questions to either the mailing lists or to look on various question 35sites such as Stack Overflow. For bug reports (where you think iperf3 36is doing something wrong) and enhancement requests (what can it do 37better), please file an issue. 38 39Thanks for your interest and support of iperf3, 40 41Bruce Mah 42Software Engineering Group 43ESnet 44