Tracking issue for release notes of #83164: Tracking Issue for const_replace

[rustbot]

This issue tracks the release notes text for #83164.

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, ...)
- [Tracking Issue for const_replace](https://github.com/rust-lang/rust/issues/83164)

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 @usbalbin -- origin issue/PR authors and assignees for starting to draft text

[usbalbin]

Ping @workingjubilee since you did the stabilization PR #130954

Not sure how release notes work, should this be its own thing or part of some bigger constification thing like your PR?

[workingjubilee]

relnotes tag goes on the PR. That PR hasn't landed yet, so this shouldn't be in relnotes.

[workingjubilee]

...oh this happens automatically on a to-announce???

[workingjubilee]

geez, there's going to be like 10 of these...

[RalfJung]

...oh this happens automatically on a to-announce???

I think it happens on FCPs. But I am not sure what event exactly the bot is looking for.

[mbartlett21]

It looks for labels of any of relnotes, relnotes-perf or finished-final-comment-period.

    if let IssuesAction::Labeled { label } = &e.action {
        if ["relnotes", "relnotes-perf", "finished-final-comment-period"]
            .contains(&label.name.as_str())
        {

https://github.com/rust-lang/triagebot/blob/f563bc9578ae26d825f0ab6b1255068afebe6a2a/src/handlers/relnotes.rs#L66-L69

[workingjubilee]

I... guess I'll do this then?

[RalfJung]

@rust-lang/release this was part of Rust 1.83. It doesn't have a milestone set because it got created from an FCP on an issue, not from a PR. So I guess it should be closed now?

It would be great if someone could document how all the new fancy release notes automation is supposed to work. Many project members can see it in action, but I assume most of us have no clue what the intended workflows here are, who is in charge of doing what, when issues like this one are to be associated with a concrete release, who closes these issues when, ...

[Mark-Simulacrum]

Closing seems reasonable. Docs also seem like a good idea, I can try to spend some time getting a write up in Forge and adding a link to it from the filed issue descriptions.

[RalfJung]

That would be great :)