Skip to content

stabilization: improve wording on how to get an FCP started #49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

stabilization: improve wording on how to get an FCP started #49

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/feature-lifecycle/stabilization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down