Skip to content
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

Updated RELEASES.md for 1.37.0 #62653

Closed
wants to merge 9 commits into from
Closed

Conversation

XAMPPRocky
Copy link
Member

Rendered

r? @Mark-Simulacrum

cc @rust-lang/release

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Jul 13, 2019
@XAMPPRocky XAMPPRocky added C-enhancement Category: An issue proposing an enhancement or a PR with one. T-release Relevant to the release subteam, which will review and decide on the PR/issue. labels Jul 13, 2019
@kennytm kennytm added the beta-nominated Nominated for backporting to the compiler in the beta channel. label Jul 13, 2019
RELEASES.md Outdated Show resolved Hide resolved
Co-Authored-By: kennytm <kennytm@gmail.com>
RELEASES.md Show resolved Hide resolved
RELEASES.md Outdated Show resolved Hide resolved
RELEASES.md Outdated Show resolved Hide resolved
RELEASES.md Outdated Show resolved Hide resolved
- [`#[must_use]` will now warn if the type is in a array and unused.][62235]
- [You can now use the `cfg` and `cfg_attr` attributes on
generic parameters.][61547]
- [You can now use enum variants through type alias.][61682] e.g. You can
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This arguably is the most important language change so I would put it first. Then I would mention consts, then Repr align. Also, I would use an example with Self here since that is likely the most common use.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that arbitrary reordering does not provide much benefit in the RELEASES.md document. This is really the point of the blog post to highlight specific features and guide a user through a new release.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reordering is not arbitrary, it's based on the relative importance of the features by estimating how many users will be affected and benefit from each one.

This is really the point of the blog post to highlight specific features and guide a user through a new release.

If so then we can dispense with examples in the release notes altogether. I think the blog post does a good job of talking in-depth about the most important bits but some users will read the release notes as well and we should use that opportunity wisely.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reordering is not arbitrary, it's based on the relative importance of the features by estimating how many users will be affected and benefit from each one.

This would be important if the entire section was longer, but it isn't. It fits entirely on the page on all devices except mobile. Personally I find this to be pointless busy work, and I'm not going to do it. If you think it's that important feel free to make a separate PR.

RELEASES.md Outdated Show resolved Hide resolved
RELEASES.md Outdated Show resolved Hide resolved
RELEASES.md Outdated Show resolved Hide resolved
RELEASES.md Outdated Show resolved Hide resolved
XAMPPRocky and others added 2 commits July 14, 2019 19:41
Co-Authored-By: Jonas Schievink <jonasschievink@gmail.com>
@ehuss
Copy link
Contributor

ehuss commented Jul 14, 2019

Have you decided how you want to link individual tool release notes?

@XAMPPRocky
Copy link
Member Author

XAMPPRocky commented Jul 15, 2019

@ehuss I figured for this release we will we just do the same as previous releases, and I'll write up the format and add more to the relnotes tool for 1.38.0, as that should give everyone plenty of time.

RELEASES.md Outdated Show resolved Hide resolved
@pietroalbini pietroalbini added the beta-accepted Accepted for backporting to the compiler in the beta channel. label Jul 16, 2019
Co-Authored-By: Josh Stone <cuviper@gmail.com>
@pietroalbini pietroalbini removed the beta-nominated Nominated for backporting to the compiler in the beta channel. label Jul 22, 2019
RELEASES.md Outdated Show resolved Hide resolved
RELEASES.md Outdated Show resolved Hide resolved
XAMPPRocky and others added 2 commits July 26, 2019 14:55
Co-Authored-By: Mark Rousskov <mark.simulacrum@gmail.com>
@edmilsonefs
Copy link

Hey! This is a ping from triage, we would like to know if you @Mark-Simulacrum could give us a few more minutes to update us from last changes made by @XAMPPRocky .

@Mark-Simulacrum
Copy link
Member

Mark-Simulacrum commented Jul 30, 2019

Modulo @Centril's comment (https://github.com/rust-lang/rust/pull/62653/files#r303208440) I think this is good to go.

Edit: would also be good to squash the commits down

@Mark-Simulacrum
Copy link
Member

Merging as #63147 since GH won't let me push to this branch for some reason (maybe because master?)

Centril added a commit to Centril/rust that referenced this pull request Jul 30, 2019
…r=Mark-Simulacrum

Updated RELEASES.md for 1.37.0

Squashed rust-lang#62653.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
beta-accepted Accepted for backporting to the compiler in the beta channel. C-enhancement Category: An issue proposing an enhancement or a PR with one. S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-release Relevant to the release subteam, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.