Stability and SemVer

async-std follows https://semver.org/.
异步std遵循https://semver.org/。

In short: we are versioning our software as MAJOR.MINOR.PATCH. We increase the:
简而言之：我们的软件版本是MAJOR.MINOR.PATCH。我们增加：

• MAJOR version when there are incompatible API changes,
• MINOR version when we introduce functionality in a backwards-compatible manner
• PATCH version when we make backwards-compatible bug fixes
  We will provide migration documentation between major versions.
• 主要版本当有不兼容的API更改时，
• 当我们以向后兼容的方式引入功能时
• 修正向后兼容错误时的补丁版本
  我们将提供主要版本之间的迁移文档。

Future expectations

未来预期

async-std uses its own implementations of the following concepts:
async std使用自己实现的以下概念：

• Read
• Write
• Seek
• BufRead
• Stream

For integration with the ecosystem, all types implementing these traits also have an implementation of the corresponding interfaces in the futures-rs library. Please note that our SemVer guarantees don't extend to usage of those interfaces. We expect those to be conservatively updated and in lockstep.
为了与生态系统集成，实现这些特性的所有类型都在futures rs库中实现了相应的接口。请注意，我们的SemVer保证不扩展到这些接口的使用。我们希望这些将被保守地更新和同步。

Minimum version policy

The current tentative policy is that the minimum Rust version required to use this crate can be increased in minor version updates. For example, if async-std 1.0 requires Rust 1.37.0, then async-std 1.0.z for all values of z will also require Rust 1.37.0 or newer. However, async-std 1.y for y > 0 may require a newer minimum version of Rust.
当前的暂定策略是，使用此crate所需的最低Rust版本可以在小版本更新中增加。例如，如果async std 1.0需要Rust 1.37.0，那么所有z值的async std 1.0.z也需要Rust 1.37.0或更高版本。但是，y>0的async std 1.y可能需要更新的Rust最低版本。
In general, this crate will be conservative with respect to the minimum supported version of Rust. With async/await being a new feature though, we will track changes in a measured pace initially.
一般情况下，该crate 对于最小支撑型的Rust是保守的。尽管async/await是一个新特性，但我们将在开始时跟踪测量速度的变化。

Security fixes

Security fixes will be applied to all minor branches of this library in all supported major revisions. This policy might change in the future, in which case we give a notice at least 3 months ahead.
安全修补程序将应用于此库所有支持的主要修订版中的所有次要分支。这项政策今后可能会改变，在这种情况下，我们至少提前3个月发出通知。

Credits

This policy is based on BurntSushi's regex crate.
此策略基于 BurntSushi's regex crate.