1.27.0 release planning

[djc]

@alex asked (privately) for a release after #3488 and #3490 so let's use this issue for tracking remaining work that we'd like to include in the next release and any other process surrounding the release process?

@rbtcollins can you share any context/thoughts around how releases have been managed in the past?

(I'm calling it 1.26.1 since I don't think there are any large changes in the public interface since the previous release, but I haven't checked that deeply so maybe 1.27.0 might be warranted?)

[rami3l]

@djc As a regular user I'd like to see 1.27.0. You got us clap4 after all (#3444).

PS: I'm still using rustup 1.26.0, so you probably meant 1.26.1 in the title?

[djc]

Ahh yes -- I somehow seemed to remember that 1.26.2 was the latest release.

So why do you think it should be 1.27.0? Just because there are "new features"?

[rami3l]

So why do you think it should be 1.27.0? Just because there are "new features"?

Do you remember the large amount of diffs that you had to change in order to pass the black box tests (for clap4)? I'm afraid someone is depending on that, though (s)he probably shouldn't.

[rami3l]

I think we can probably add a new milestone here? There are a few PRs that I want to address before cutting a new release 👀

[djc]

That works too. I like having a release planning issue because it's something interested users can subscribe to to keep up to date with the progress and comments can be added to discuss scope changes -- so in other projects I usually like to use task lists in a planning issue like this one.

[rami3l]

@djc Good. Let's keep it this way then.

I'll keep my list of issues "of interest" here:

• Refine suggestions about missing components #3453
• Add support for fish shell #3108
  • Add suggestions to mention sourcing env.fish #3506
• rustup-init.sh ksh and zsh compatibility fixes #3475
• Remove redundant message if an error occurs during package extraction #3464
• Warn when running under Rosetta emulation #3068
• Make rustup show output info in a more logical order #3225

The idea is that these are mostly PRs that have been reviewed but require checking again.

[rbtcollins]

The release process is documented in the rustup contributors guide. https://rust-lang.github.io/rustup/dev-guide/release-process.html

[tribal] We often ask for testers on reddit / rust-users
[tribal] we always increment the minor number unless [a] major compat break (which we haven't had : we've done minor compat breaks without bumping the major number), and [b] its a hotfix because the last release had a defect.

So the next # should 1.27.0

[alex]

Looks like we're down to a single issue remaining from the original list. Is there anything else for consideration for 1.27.0?