Lines Matching +full:update +full:- +full:commit +full:- +full:hash
12 -------------
14 The developer list for iperf3 is: iperf-dev@googlegroups.com.
17 http://groups.google.com/group/iperf-dev
21 acceptable. If necessary, a user-oriented mailing list might be
25 -----------
38 ----------------------
43 -V, --verbose more detailed output than before
44 -J, --json output in JSON format
45 -Z, --zerocopy use a 'zero copy' sendfile() method of sending data
46 -O, --omit N omit the first n seconds (to ignore slowstart)
47 -T, --title str prefix every output line with this string
48 -F, --file name xmit/recv the specified file
49 -A, --affinity n/n,m set CPU affinity (Linux and FreeBSD only)
50 -k, --blockcount #[KMG] number of blocks (packets) to transmit (instead
51 of -t or -n)
52 -L, --flowlabel set IPv6 flow label (Linux only)
56 -C, --linux-congestion set congestion control algorithm (Linux only)
57 (-Z in iperf2)
62 -d, --dualtest Do a bidirectional test simultaneously
63 -r, --tradeoff Do a bidirectional test individually
64 -T, --ttl time-to-live, for multicast (default 1)
65 -x, --reportexclude [CDMSV] exclude C(connection) D(data) M(multicast)
67 -y, --reportstyle C report as a Comma-Separated Values
73 ------------
82 * The ``-Z`` flag sometimes causes the iperf3 client to hang on OSX.
85 * When specifying the TCP buffer size using the ``-w`` flag on Linux,
88 iperf3's ``--debug`` flag.) However, CWND does not actually ramp up
93 * Although the ``-w`` flag is documented as setting the (TCP) window
95 shown to be helpful with high-bitrate UDP tests.
103 correctly reflect the client-side measurements. This is due to the
116 ----------
126 * *MINOR* version when adding functionality in a backwards-compatible manner, and
128 * *PATCH* version when making backwards-compatible bug fixes.
131 -----------------------------
133 1. Update the ``README`` and ``RELEASE_NOTES`` files to be accurate. Make sure
145 vi RELEASE_NOTES # update version number and release date
146 vi configure.ac # update version parameter in AC_INIT
147 vi src/iperf3.1 # update manpage revision date if needed
148 vi src/libiperf.3 # update manpage revision date if needed
149 git commit -a # commit changes to the local repository only
151 git commit -a # commit changes to the local repository only
155 ./make_release tar $VERSION # create tarball and compute SHA256 hash
163 pre-testing.
165 4. Stage the tarball (and a file containing the SHA256 hash) to the
177 smoke-testing the results of the tarball on all supported
182 9. PGP-sign the release announcement text using ``gpg --clearsign``.
186 by other, non-email means.
189 finalized. To commit the release-engineering-related changes to
193 git push --tags # Push the new tag to the GitHub repo
195 11. Send the PGP-signed release announcement to the following
201 * iperf-dev@googlegroups.com
203 * iperf-users@lists.sourceforge.net
205 * perfsonar-user@internet2.edu
207 * perfsonar-developer@internet2.edu
209 Note: Thunderbird sometimes mangles the PGP-signed release
212 lines (such as the SHA256 hash). Apple Mail and mutt seem to
217 12. Update the iperf3 Project News section of the documentation site
222 13. If an update to the on-line manual page is needed, it can be
228 nroff -Tascii -c -man src/iperf3.1 | ul | sed 's/^/ /' > iperf3.txt
231 ------------