# Rust 1.16 release status

**URL:** https://internals.rust-lang.org/t/rust-1-16-release-status/4802
**Category:** Uncategorized
**Created:** [February 17, 2017, 2:38am UTC](https://internals.rust-lang.org/t/rust-1-16-release-status/4802 "2017-02-17T02:38:20Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![brson](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/brson/32/5197_2.png) [@brson](https://internals.rust-lang.org/u/brson)
#### Post date: [February 17, 2017, 2:38am UTC](https://internals.rust-lang.org/t/rust-1-16-release-status/4802/1 "2017-02-17T02:38:20Z")

</div>

Rust 1.16 is scheduled to be released March 16. It’s a modest release but there are some goodies in it like `cargo check` and several ergonomic improvements: [release notes](https://github.com/rust-lang/rust/pull/39835).

Oh, also there are [**9 bugs filed against beta**](https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3Aregression-from-stable-to-beta). Oh my! There’s less time than you might think to get these pinned down. Let’s do our best! I know we can. Last time we fixed all the bugs we knew about before release, and that was kinda great.

There are also 5 issues on the [1.16.0 milestone](https://github.com/rust-lang/rust/milestone/33). This is the first release milestone we’ve used in a while, and it’s tracking a few things that must happen before the release.

To leave us breathing room in the schedule, please endeavor to **have beta backports in by March 3**. That is two weeks from now.

Beyond 1.16 there are more great things on the horizon: see [release milestone predictions](https://internals.rust-lang.org/t/rust-release-milestone-predictions/4591).

---

<div class="post-metadata">

### Author: ![alexcrichton](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/alexcrichton/32/4501_2.png) [@alexcrichton](https://internals.rust-lang.org/u/alexcrichton)
#### Post date: [February 17, 2017, 3:49pm UTC](https://internals.rust-lang.org/t/rust-1-16-release-status/4802/2 "2017-02-17T15:49:41Z")

</div>

I just did a bit of triage of the open bugs and closed 3 as a few dupes. Of the remaining 2 are scheduled to be discussed with @rust-lang/libs, one has a PR against cargo, two are assigned to @arielb1, and one is assigned to me.

The [one assigned to me](https://github.com/rust-lang/rust/issues/39504) I could use some help with, though. I haven’t been able to track down what’s happening yet and have been running low on time to give it a proper investigation.

---

<div class="post-metadata">

### Author: ![brson](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/brson/32/5197_2.png) [@brson](https://internals.rust-lang.org/u/brson)
#### Post date: [February 17, 2017, 7:46pm UTC](https://internals.rust-lang.org/t/rust-1-16-release-status/4802/3 "2017-02-17T19:46:12Z")

</div>

Thanks @alexcrichton!

---

<div class="post-metadata">

### Author: ![chriskrycho](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/chriskrycho/32/12576_2.png) [@chriskrycho](https://internals.rust-lang.org/u/chriskrycho)
#### Post date: [February 17, 2017, 11:23pm UTC](https://internals.rust-lang.org/t/rust-1-16-release-status/4802/4 "2017-02-17T23:23:57Z")

</div>

Question: the release notes don’t mention `cargo check`; is that an oversight, intentional, etc.? (Just happened to be poking around and noticed it.)

---

<div class="post-metadata">

### Author: ![brson](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/brson/32/5197_2.png) [@brson](https://internals.rust-lang.org/u/brson)
#### Post date: [February 17, 2017, 11:35pm UTC](https://internals.rust-lang.org/t/rust-1-16-release-status/4802/5 "2017-02-17T23:35:28Z")

</div>

@chriskrycho It’s an oversight. The release notes need to be edited to add `cargo check`.

---

<div class="post-metadata">

### Author: ![brson](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/brson/32/5197_2.png) [@brson](https://internals.rust-lang.org/u/brson)
#### Post date: [March 2, 2017, 1:18am UTC](https://internals.rust-lang.org/t/rust-1-16-release-status/4802/6 "2017-03-02T01:18:19Z")

</div>

OK, I’m all caught up on triage of 1.16 issues, and it’s looking pretty ok! Remember 1.16 comes out on 3/16. We’ll aim to start a build on 3/10. And it’s already 3/1!

There’s only one outstanding beta regression, and it’s a release blocker:

- [cargo needs to be updated so that 1.17 can bootstrap off 1.16](https://github.com/rust-lang/rust/issues/39504). That’s not great! AIUI @alexcrichton needs help with this.

There are two additional things on the [1.16 milestone](https://github.com/rust-lang/rust/milestone/33), but they are small matters.

A few new [stable regressions](https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3Aregression-from-stable-to-stable) have appeared, as well as [nightly](https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3Aregression-from-stable-to-nightly).

---

<div class="post-metadata">

### Author: ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/system/32/14092_2.png) [@system](https://internals.rust-lang.org/u/system)
#### Post date: [March 25, 2019, 8:27am UTC](https://internals.rust-lang.org/t/rust-1-16-release-status/4802/7 "2019-03-25T08:27:58Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
