Updates to 1.12.1

Author: brson

_posts/2016-10-20-Rust-1.12.1.md

@@ -4,12 +4,12 @@ title: "Announcing Rust 1.12.1"
 author: The Rust Core Team
 ---
 
-The Rust team is happy to announce the latest version of Rust, 1.12.1. Rust is
-a systems programming language with the slogan "fast, reliable, productive:
-pick three."
+The Rust team is happy to announce the latest version of Rust, 1.12.1. Rust is a
+systems programming language with a focus on reliability, performance, and
+concurrency.
 
 As always, you can [install Rust 1.12.1][install] from the appropriate page on our
-website.
+website, or install via [rustup] with `rustup update stable`.
 
 [install]: https://www.rust-lang.org/install.html
 
@@ -58,14 +58,6 @@ regressions that we hadn't detected in our testing. Not all of them are
 directly MIR related, but when you change the compiler internals so much, it's
 bound to ripple outward through everything.
 
-One of these bugs even prevented a production user, [Ethcore], from building on
-Rust 1.12 stable. This is further compounded by [a DoS attack] against the
-Etherium network itself, and so the project is recommending that all Etherium
-users switch to Parity. When it rains, it pours.
-
-[Ethcore]: https://github.com/ethcore/parity
-[a DoS attack]: https://blog.ethereum.org/2016/09/22/ethereum-network-currently-undergoing-dos-attack/
-
 ### Why make a point release?
 
 Now, given that we have a six-week release cycle, and we're halfway towards
@@ -74,29 +66,34 @@ Rust 1.13, you may wonder why we're choosing to cut a patch version of Rust
 previously said something like "point releases should only happen in extreme
 situations, such as a security vulnerability in the standard library."
 
-The Rust team cares deeply about the stability of Rust, and about our users,
-both production and non. We could have told you all to wait, but we want you to
-know how seriously we take this stuff. We think it's worth it to demonstrate
-our commitment to you by putting in the work of making a patch release in this
+The Rust team cares deeply about the stability of Rust, and about our users'
+experience with it. We could have told you all to wait, but we want you to know
+how seriously we take this stuff. We think it's worth it to demonstrate our
+commitment to you by putting in the work of making a point release in this
 situation.
 
 Furthermore, given that this is not security related, it's a good time to
-practice actually cutting a patch release. We've never done it before, and the
-release process is [semi-automated] but still not completely so. Having a patch
-release in the world will also shake out any bugs in dealing with patch
-releases in other tooling as well, like [rustup]. Making sure that this all
-goes smoothly and getting some practice going through the motions will be
-useful if we ever need to cut some sort of *emergency* patch release due to
-a security advisory or anything else.
+practice actually cutting a point release. We've never done it before, and the
+release process is [semi-automated] but still not completely so. Having a point
+release in the world will also [shake out any bugs][bugs] in dealing with point
+releases in other tooling as well, like [rustup]. Making sure that this all goes
+smoothly and getting some practice going through the motions will be useful if
+we ever need to cut some sort of *emergency* point release due to a security
+advisory or anything else.
 
 [semi-automated]: https://forge.rust-lang.org/release-process.html
-[rustup]: http://rustup.rs/
+[rustup]: https://www.rustup.rs/
+[bugs]: https://github.com/rust-lang/rust/pull/37173#issuecomment-253938822
+
+This is the first Rust point release since [Rust 0.3.1], all the way back in in
+2012, and marks 72 weeks since Rust 1.0, when we established our six week
+release cadence along with a commitment to aggressive stability
+guarantees. While we're disappointed that 1.12 had these regressions, we're
+really proud of Rust's stability and will to continue expanding our efforts to
+ensure that it's a platform you can rely on. We want Rust to be the most
+reliable programming platform in the world.
 
-It is true that regular patch releases would indicate that something is deeply
-wrong with our process. However, we've gone 72 weeks past Rust 1.0 without
-needing to do a point release, so we feel that we've been doing well so far.
-We're going to continue to closely monitor all of this to ensure that this
-isn't a sign of something more deeply wrong with our release engineering.
+[Rust 0.3.1]: https://mail.mozilla.org/pipermail/rust-dev/2012-July/002152.html
 
 ### A note about testing on beta
 
@@ -163,7 +160,7 @@ as possible as well.
 * [ICE, possibly related to associated types of associated types?][36325]
 * [Compilation of a crate using a large static map fails on latest i686-pc-windows-gnu Beta][36799]
 * [Regression: "no method found" error when calling same method twice, with HRTB impl][37154]
-* [ ICE: fictitious type <i32 as ToRef>::Ref in sizing_type_of()][37109]
+* [ICE: fictitious type sizing_type_of][37109]
 
 [36325]: https://github.com/rust-lang/rust/issues/36325
 [36799]: https://github.com/rust-lang/rust/issues/36799