-
Notifications
You must be signed in to change notification settings - Fork 303
add blog post announcing Rust 2021 public testing period #866
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add blog post announcing Rust 2021 public testing period #866
Conversation
Addressed review comments. I also noticed the file had a rather undescriptive name, so I gave it a better one. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
4. Run `cargo +nightly check` to verify it now works in the new edition. | ||
|
||
**Note that Rust 2021 is still unstable, so you can expect bugs and other changes!** We recommend migrating your crates in a temporary copy of your code versus your main branch. If you do encounter problems, or find areas where quality could be improved (missing documentation, confusing error messages, etc) please [file an issue](https://github.com/rust-lang/rust/issues/new/choose) and tell us about it! Thank you! | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to provide some forum for positive experiences? Maybe e.g. an internals or users.r-l.o thread might work well here...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a nice thought. Internals thread sounds good. The only thing is that I don't want to give the implication that we are monitoring it. (At least, I know I won't be able to, can't speak for everyone.)
|
||
### What comes next | ||
|
||
We are targeting stabilization of all Rust 2021 for Rust 1.56, which will be released on October 21st, 2021. Per the [Rust train release model](https://doc.rust-lang.org/book/appendix-07-nightly-rust.html), that means all features and work must be landed on nightly by September 7th. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know there was some discussion on these dates, but can we triple check that we're on a good path to make these dates?
…-public-testing.md
Per discussion with @rylev, I updated the date on the post to next Tuesday. We're closing out a few lingering issues before we are ready to post. |
…-public-testing.md
Clarify that this is the nightly edition guide
Dear @rust-lang/core -- we believe this post is ready to merge! |
Per our plans, we want to announce a "public testing period" to encourage folks to try out the edition on nightly. I've dated this post for a week from now, both to give folks time to review and to give us time to close a few more bugs. =)
Before merging this PR, please do a final check with @rust-lang/project-edition-2021 to make sure we are in a good state to go forward in terms of documentation and known bugs!
If you'd like to track status, check out the https://github.com/orgs/rust-lang/projects/7 project board.