Skip to content

posts: announce rustup 1.28.2 #1593

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

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rami3l
Copy link
Member

@rami3l rami3l commented Apr 25, 2025

cc @rust-lang/rustup

Rendered

@rami3l rami3l marked this pull request as draft April 25, 2025 13:50
@rami3l
Copy link
Member Author

rami3l commented Apr 25, 2025

Sorry, I forgot to mark it as draft 🙈 it shouldn't be merged before the release really happens.

@rami3l rami3l force-pushed the post/rustup-1-28-2 branch from 558f131 to b33ae58 Compare April 25, 2025 13:53
@rami3l rami3l requested a review from shepmaster April 25, 2025 14:01
Copy link
Member

@shepmaster shepmaster left a comment

Choose a reason for hiding this comment

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

Since you asked for it, I put more effort into reading and thinking about what the text meant. Feel free to take or leave any of the suggestions and pay attention to or ignore any of the clarification questions though.

Copy link
Member

Choose a reason for hiding this comment

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

I am aware that we have a call-for-testing post in https://internals.rust-lang.org/t/seeking-beta-testers-for-rustup-v1-28-2. Do we want to call for testing also in the "Inside Rust Blog"? I could see this is a patch version release so we skip that part :)

Copy link
Member

Choose a reason for hiding this comment

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

Oh it might also be worth mentioning this on zulip. One of the things brought up before is that many people involved with rust don't read internals whereas zulip is more active.

Copy link
Member Author

@rami3l rami3l Apr 28, 2025

Choose a reason for hiding this comment

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

@weihanglo That might indeed be a good idea in general, but the scope of this patch release is relatively small IMHO.

@ChrisDenton The Zulip thing does sound like a good idea. Where are we supposed to post it though?

Copy link
Member

Choose a reason for hiding this comment

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

@rami3l We should post in general for visibility I think because it should have a wide audience.

Copy link
Member

Choose a reason for hiding this comment

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

Perhaps it should link to a t-rustup thread (or vice versa) so there's a cross-reference of where rustup discussions have happened on zulip.

Copy link
Member Author

Choose a reason for hiding this comment

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

@rami3l rami3l force-pushed the post/rustup-1-28-2 branch 2 times, most recently from c5daca6 to 0386140 Compare April 28, 2025 15:45
@rami3l rami3l force-pushed the post/rustup-1-28-2 branch from 0386140 to 9a75051 Compare April 29, 2025 13:32
@rami3l rami3l force-pushed the post/rustup-1-28-2 branch 2 times, most recently from 6e19225 to ccdad6c Compare April 29, 2025 13:50
@rami3l rami3l force-pushed the post/rustup-1-28-2 branch from ccdad6c to c21b6c6 Compare April 29, 2025 13:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants