Repository navigation
1.27.0 release planning #3501
Description
@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?)
Reacted by rami
Activity
rami3l commentedon Oct 5, 2023
@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 meant1.26.1in the title?[-]1.26.3 release planning[/-][+]1.26.1 release planning[/+]djc commentedon Oct 5, 2023
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"?
[-]1.26.1 release planning[/-][+]1.27.0 release planning[/+]rami3l commentedon Oct 5, 2023
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 commentedon Oct 5, 2023
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 commentedon Oct 5, 2023
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 commentedon Oct 5, 2023
@djc Good. Let's keep it this way then.
I'll keep my list of issues "of interest" here:
env.fish#3506rustup showoutput info in a more logical order #3225The idea is that these are mostly PRs that have been reviewed but require checking again.
rbtcollins commentedon Oct 6, 2023
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 commentedon Nov 17, 2023
Looks like we're down to a single issue remaining from the original list. Is there anything else for consideration for 1.27.0?
heiher commentedon Nov 17, 2023
rami3l commentedon Feb 10, 2024
There are a few things to be done in order to actually release v1.27.0:
tracing_opentelemetryupdate, mergechore(deps): update opentelemetry #3683Upgrade to opentelemetry 0.22 #3694.CHANGELOGfor v1.27.0 #3699, update the changelog to match dist: bumprustupversion to1.27.0#3653.rustup-init.sh#3700, update the shasum (and date) inrustup-init.shto point to the latest commit on themasterbranch.mastertostableand wait for the stable CI to turn green.release-process.mdto match the new workflow based on GitHub Merge Queue #3672.djc commentedon Feb 27, 2024
Note: we have a candidate release out for testing right now, see https://internals.rust-lang.org/t/seeking-beta-testers-for-rustup-1-27-0/20352/7.
Please send your feedback there or in this issue.
alex commentedon Mar 12, 2024
Release is out! I think we can close this.