Lines Matching refs:a
20 a low volume of inquiries on the developer list is probably
21 acceptable. If necessary, a user-oriented mailing list might be
27 Before submitting a bug report, try checking out the latest version of
41 for a complete list of iperf3 options)::
45 -Z, --zerocopy use a 'zero copy' sendfile() method of sending data
62 -d, --dualtest Do a bidirectional test simultaneously
63 -r, --tradeoff Do a bidirectional test individually
67 -y, --reportstyle C report as a Comma-Separated Values
76 interest to a large fraction of users or have high impact for some
99 doing a ``make install`` before the ``iperf3`` executable can find
102 * The results printed on the server side at the end of a test do not
107 * The server could have a very short measurement reporting interval at
108 the end of a test (particularly a UDP test), containing few or no
118 iperf3 version numbers use (roughly) a `Semantic Versioning
126 * *MINOR* version when adding functionality in a backwards-compatible manner, and
137 2. Compose a release announcement. Most of the release announcement
139 announcement can be used as a starting point.
141 3. Preferably starting from a clean source tree (be sure that ``git
149 git commit -a # commit changes to the local repository only
151 git commit -a # commit changes to the local repository only
154 ./make_release tag $VERSION # this creates a tag in the local repo
157 These steps should be done on a platform with a relatively recent
162 The result will be a release artifact that should be used for
165 4. Stage the tarball (and a file containing the SHA256 hash) to the
169 downloading a fresh copy of the file and verifying the SHA256
173 6. Also verify (with file(1)) that the tarball is actually a gzipped
183 The signed announcement will be sent out in a subsequent emails,
185 allows a signed release announcement to be resent via email or sent
214 sending process by sending a copy to oneself first and attempting
219 ``docs/conf.py`` in the source tree) and deploy a new build of the