Tracking issue for release notes of #128316: Stabilize most of `io_error_more`

rustbot commented 3 weeks ago

This issue tracks the release notes text for #128316.

Steps

[ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
[ ] Issue is nominated for release team review of clarity for wider audience.
[ ] Release team includes text in release notes/blog posts.

Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Stabilize most of `io_error_more`](https://github.com/rust-lang/rust/pull/128316)

[!TIP] Use the previous releases categories to help choose which one(s) to use. The category will be de-duplicated with all the other ones by the release team.

More than one section can be included if needed.

Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section. Otherwise leave it empty.

cc @GrigorenkoPV, @dtolnay -- origin issue/PR authors and assignees for starting to draft text

GrigorenkoPV commented 3 weeks ago

From what I can tell, this should be just closed, because it's simply API stabilization: https://github.com/rust-lang/rust/issues/130825#issuecomment-2384561081

@rustbot close

(Probably don't have enough rights for that)

rustbot commented 3 weeks ago

Error: The feature close is not enabled in this repository. To enable it add its section in the triagebot.toml in the root of the repository.

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #t-infra on Zulip.

joboet commented 2 weeks ago

Correct me if I'm wrong, but shouldn't release tracking issues stay open until the change has actually been included in the release notes?

rust-lang / rust