1*7ab6e6acSAndroid Build Coastguard WorkerSubject: iperf3 status, June 2017 2*7ab6e6acSAndroid Build Coastguard Worker 3*7ab6e6acSAndroid Build Coastguard Workeriperf 3.2 Release Plans 4*7ab6e6acSAndroid Build Coastguard Worker----------------------- 5*7ab6e6acSAndroid Build Coastguard Worker 6*7ab6e6acSAndroid Build Coastguard WorkerWe've done quite a bit of work the past few weeks getting the master 7*7ab6e6acSAndroid Build Coastguard Workerbranch in shape to cut a new release, which will be the first of the 8*7ab6e6acSAndroid Build Coastguard Worker3.2.x series. These changes include fixes for a number of 9*7ab6e6acSAndroid Build Coastguard Workerlong-standing bugs (such as some of the statistics computation, and 10*7ab6e6acSAndroid Build Coastguard Workerfixes for --file), as well as new features (for example optional 11*7ab6e6acSAndroid Build Coastguard Workerauthentication and a configurable client connection timeout) and 12*7ab6e6acSAndroid Build Coastguard Workergeneral improvements (better timing for the --bitrate/--bandwidth 13*7ab6e6acSAndroid Build Coastguard Workeroptions). 14*7ab6e6acSAndroid Build Coastguard Worker 15*7ab6e6acSAndroid Build Coastguard WorkerWe'd like to encourage users in the community who are comfortable 16*7ab6e6acSAndroid Build Coastguard Workercompiling iperf3 from GitHub sources, to checkout / clone the iperf3 17*7ab6e6acSAndroid Build Coastguard Workermaster branch from GitHub and try it out in their environments. (No 18*7ab6e6acSAndroid Build Coastguard Workertarballs will be produced until the official 3.2 release, although I'd 19*7ab6e6acSAndroid Build Coastguard Workersay we're basically in "release candidate" stage now.) 20*7ab6e6acSAndroid Build Coastguard Worker 21*7ab6e6acSAndroid Build Coastguard WorkerThere is a mostly-final set of release notes in the RELEASE_NOTES file 22*7ab6e6acSAndroid Build Coastguard Workeron master, so you can see what's new, changed, fixed, and so on. 23*7ab6e6acSAndroid Build Coastguard Worker 24*7ab6e6acSAndroid Build Coastguard WorkerAssuming no serious problems, we're aiming for an official release in 25*7ab6e6acSAndroid Build Coastguard Workermid- to late-June (2017!). 26*7ab6e6acSAndroid Build Coastguard Worker 27*7ab6e6acSAndroid Build Coastguard Workeriperf3 Support 28*7ab6e6acSAndroid Build Coastguard Worker-------------- 29*7ab6e6acSAndroid Build Coastguard Worker 30*7ab6e6acSAndroid Build Coastguard WorkerAfter a lot of issue triage, we're down to 38 issues in the issue 31*7ab6e6acSAndroid Build Coastguard Workertracker (plus three outstanding pull requests). As mentioned in an 32*7ab6e6acSAndroid Build Coastguard Workerearlier update, a lot of the issues we closed were user questions, not 33*7ab6e6acSAndroid Build Coastguard Workerbug reports or enhancement requests. We'd like to direct user 34*7ab6e6acSAndroid Build Coastguard Workerquestions to either the mailing lists or to look on various question 35*7ab6e6acSAndroid Build Coastguard Workersites such as Stack Overflow. For bug reports (where you think iperf3 36*7ab6e6acSAndroid Build Coastguard Workeris doing something wrong) and enhancement requests (what can it do 37*7ab6e6acSAndroid Build Coastguard Workerbetter), please file an issue. 38*7ab6e6acSAndroid Build Coastguard Worker 39*7ab6e6acSAndroid Build Coastguard WorkerThanks for your interest and support of iperf3, 40*7ab6e6acSAndroid Build Coastguard Worker 41*7ab6e6acSAndroid Build Coastguard WorkerBruce Mah 42*7ab6e6acSAndroid Build Coastguard WorkerSoftware Engineering Group 43*7ab6e6acSAndroid Build Coastguard WorkerESnet 44