| % Release Channels |
| |
| <small>There is a new edition of the book and this is an old link.</small> |
| |
| > The Rust project uses a concept called ‘release channels’ to manage releases. |
| > New nightly releases are created once a day. |
| > Every six weeks, the latest nightly release is promoted to ‘Beta’. |
| > At that point, it will only receive patches to fix serious errors. |
| > Six weeks later, the beta is promoted to ‘Stable’. |
| |
| --- |
| |
| This chapter does not exist yet in [the second edition][2]. |
| You can check out other resources that describe release channels. |
| |
| * **[In the Rustup documentation: Keeping Rust Up-to-date][4]** |
| * [On the website: Install Rust][5] |
| * [In the Rust RFCs: RFC 507 — Release Channels][3] |
| * [in the current edition: How Rust is Made and “Nightly Rust”][2] |
| * <small>[In the first edition: Ch 4.11 — Release Channels][1]</small> |
| |
| |
| [1]: https://doc.rust-lang.org/1.30.0/book/first-edition/release-channels.html |
| [2]: appendix-07-nightly-rust.html |
| [3]: https://github.com/rust-lang/rfcs/blob/master/text/0507-release-channels.md |
| [4]: https://github.com/rust-lang-nursery/rustup.rs/blob/master/README.md#keeping-rust-up-to-date |
| [5]: https://www.rust-lang.org/en-US/tools/install |
| |
