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

Rust 1.26.1 point release #50756

Closed
pietroalbini opened this issue May 14, 2018 · 17 comments
Closed

Rust 1.26.1 point release #50756

pietroalbini opened this issue May 14, 2018 · 17 comments
Labels
C-feature-request Category: A feature request, i.e: not implemented / a PR. T-core Relevant to the core team, which will review and decide on the PR/issue. T-release Relevant to the release subteam, which will review and decide on the PR/issue.

Comments

@pietroalbini
Copy link
Member

pietroalbini commented May 14, 2018

Note: there is no decision on whether 1.26.1 should be released yet. This is just a wishlist.

There are a few bad bugs in the 1.26.0 release, and there is a discussion (#50646 (comment)) about making a point release with a few backports. This issue tracks the PRs we would like to backport, and if we should do the point release at all.

cc @rust-lang/release @rust-lang/core


@pietroalbini pietroalbini added the T-release Relevant to the release subteam, which will review and decide on the PR/issue. label May 14, 2018
@kennytm kennytm added T-core Relevant to the core team, which will review and decide on the PR/issue. I-nominated C-feature-request Category: A feature request, i.e: not implemented / a PR. labels May 14, 2018
@leoyvens
Copy link
Contributor

leoyvens commented May 14, 2018

I'd like to propose #50694 for an eventual point release, it makes impl Trait work with a bunch of common traits that have a Self default (impl PartialEq, impl Add, ...) rather than stack overflow.

@BatmanAoD
Copy link
Member

It sounds like #50646 has already been fixed in the beta channel. Does the backport require a new PR?

@sanxiyn
Copy link
Member

sanxiyn commented May 15, 2018

#49462 affects ARM as well as FreeBSD. I think the point release is warranted.

@smmalis37
Copy link
Contributor

I'd like to strongly vote in favor of a point release containing the fix for #50646.

@est31
Copy link
Member

est31 commented May 15, 2018

We should also backport #49523. Right now the distributed source of the 1.26.0 release artifacts don't contain release notes for the 1.26.0 release, which is bad.

@nrc
Copy link
Member

nrc commented May 15, 2018

We're getting quite a lot of reports of problems on the RLS repo, so I'd be in favour of a point release for the RLS. I'll put together a PR.

I'd also like to update rustfmt due to rust-lang/rustfmt#2695

@nrc
Copy link
Member

nrc commented May 16, 2018

PR for RLS/Rustfmt: #50794

@kennytm
Copy link
Member

kennytm commented May 16, 2018

I nominate #50811 to be included.

@nrc
Copy link
Member

nrc commented May 17, 2018

Discussed and approved at today's core team meeting. We wanted to include RLS/Rustfmt, termination trait, NaN in consts, and missing manifests (they were all decided either to be high reward or low risk enough to justify inclusion).

@leoyvens
Copy link
Contributor

@nrc Did #50694 get discussed? It's already accepted and merged for beta, got 3 issue reports and the patch was minor.

@nrc
Copy link
Member

nrc commented May 17, 2018

Did #50694 get discussed? It's already accepted and merged for beta, got 3 issue reports and the patch was minor.

No. We missed that one. Ping @rust-lang/core - how do we feel about another inclusion?

@nrc
Copy link
Member

nrc commented May 17, 2018

iiuc it is not a stability concern, just a bug-fix since we currently stack overflow. It looks like a non-trivial patch to me, but I'm not in a great place to judge. Seems like we could live without it.

@eedahl
Copy link

eedahl commented May 19, 2018

Added some recent errors to #50646, currently happening on nightly, jic they're of relevance.

@Mark-Simulacrum
Copy link
Member

The point release PR is up. I believe it includes all items we'd like to; if your desired PR wasn't included please let me know.

@sinesc
Copy link

sinesc commented May 25, 2018

Is this testable via rustup or download?

@pietroalbini
Copy link
Member Author

There is no build yet, after the PR will be merged a build will appear in the dev-static bucker.

bors added a commit that referenced this issue May 25, 2018
Stable point release (1.26.1)

This includes all items on [the wishlist](#50756), plus #50694, which backported cleanly.

The target date is May 29th, Tuesday next week.

cc @rust-lang/compiler @oli-obk @eddyb  -- I backported #50812, but it wasn't a clean patch so review would be appreciated.
@Mark-Simulacrum
Copy link
Member

Release artifacts are built, you can run RUSTUP_DIST_SERVER=https://dev-static.rust-lang.org rustup update stable to test it locally -- please report problems at https://internals.rust-lang.org/t/rust-1-26-1-prerelease-testing/ or here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature-request Category: A feature request, i.e: not implemented / a PR. T-core Relevant to the core team, which will review and decide on the PR/issue. T-release Relevant to the release subteam, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests