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