From 8bdebdfaeeb39e59a2207ec621c0db099d953e1d Mon Sep 17 00:00:00 2001 From: Xiretza Date: Sun, 8 Jan 2023 12:12:51 +0100 Subject: [PATCH] stabilization: improve wording on how to get an FCP started --- src/feature-lifecycle/stabilization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/feature-lifecycle/stabilization.md b/src/feature-lifecycle/stabilization.md index 3722f8e..e59fba1 100644 --- a/src/feature-lifecycle/stabilization.md +++ b/src/feature-lifecycle/stabilization.md @@ -29,7 +29,7 @@ You can see an example of a stabilization report in [#88581](https://github.com/ ## Before writing a PR to stabilize a feature -Check to see if a FCP has completed first. If not, either ping `@rust-lang/libs-api` or leave a comment asking about the status of the feature. +Check to see if a FCP has completed first. If not, leave a comment in the tracking issue asking about the status of the feature. If you are a member of the rust-lang GitHub organization, ping `@rust-lang/libs-api` in the comment. This will save you from opening a stabilization PR and having it need regular rebasing while the FCP process runs its course.