Update documentation - #2014
Merged
Merged
Conversation
* Update release engineering checklist to reflect current practices. * Updates for support-ish things * Remove "Changes from iperf2" section because it's pretty obsolete/ wrong at this point.
Add a note in the README about what iperf3 is used for and by whom. Other text maintenance.
swlars
approved these changes
Mar 26, 2026
swlars
left a comment
Contributor
There was a problem hiding this comment.
Looks good! Thanks for updating!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version of iperf3 (or development branch, such as
masteror3.1-STABLE) to which this pull request applies:masterIssues fixed (if any): None
Brief description of code changes (suitable for use as a commit message):
Update of documentation, primarily in the area of release engineering, but also regarding iperf3's different audiences.