Add release notes for 1.92.0

[cuviper]

cc @rust-lang/release r? @BoxyUwU

[rustbot]

BoxyUwU is currently at their maximum review capacity. They may take a while to respond.

[cuviper]

@rustbot ping relnotes-interest-group

[rustbot]

Hi relnotes-interest-group, this issue/PR could use some help in reviewing / adjusting release notes. Could you take a look if available? Thanks <3

cc @alex-semenyuk @jieyouxu @joshtriplett @Kobzol @lcnr @traviscross

[Kivooeo]

Hi, sorry for being late with this

I wanted to ask about Release Notes for this change (https://github.com/rust-lang/rust/issues/146810). We discussed this briefly on #t-compiler > Determining if a change needs release notes, but I’m still not completely sure whether they are required in my case. If they are needed, do I still have time to add them?

[cuviper]

@Kivooeo that change is already included, but you can still suggest edits here, even removing that line if you don't think it deserves mention.

[Kivooeo]

I meant a release blog section like here https://github.com/rust-lang/rust/issues/147383

Because I still unsure about what changes require them

If this change is notable enough for inclusion in the blog post then this section should be edited to contain a draft for the blog post. Otherwise leave it empty.

This line is not clear enough to me, how can I understand if change is "notable enough"

[cuviper]

Ah, the blog is much more subjective -- there's no real requirement, but it's essentially a judgement call about how many people may care about the change. @BoxyUwU is handling that in https://github.com/rust-lang/blog.rust-lang.org/pull/1757.

[BoxyUwU]

this is now in the stable PR. if the commits could be squashed then this can be r+'d

[cuviper]

@bors r=BoxyUwU rollup

[bors]

:pushpin: Commit 90d2477e4e35927b20237b27869200fb1d47e7bf has been approved by BoxyUwU

It is now in the queue for this repository.