Repository navigation
Tracking issue for release notes of #155942: Stabilize -Zprofile-sample-use #161171
Description
Activity
@folkertdev Since #155942 was successfully merged, let's discuss the Release notes.
Answer to the questions from the template above:
Does this need an additional compat notes section?
No, it doesn't since we only stabilize a compiler flag. It should be obvious enough that stabilization means replacing
-Zprofile-sample-usewith-Cprofile-sample-use. However, even this detail is not critical since the only known user of this flag in open-source is RustForLinux (and they are already notified about this one).Was this a libs stabilization that should have additional headers to list new APIs under Stabilized APIs and Const Stabilized APIs?
No, it's not a lib stabilization - it's a compiler switch stabilization.
I think the change is quite small and niche so no dedicated release blog section is required here.
thanks!
This issue tracks the release notes text for #155942.
cc @zamazan4ik, @folkertdev -- original issue/PR authors and assignees for drafting text
See the forge.rust-lang.org chapter about release notes for an overview of how the release team makes use of these tracking issues.
Release notes text
This section should be edited to specify the correct category(s) for the change, with succinct description(s) of what changed. Some things worth considering:
Stabilized APIsandConst Stabilized APIs?Tip
Use the previous releases for inspiration on how to write the release notes text and which categories to pick.
Release blog section
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.
Note
If a blog post section is required the
release-blog-postlabel should be added (@rustbot label +release-blog-post) to this issue as otherwise it may be missed by the release team.