Skip to content

Commit

Permalink
Change the feature used as an example of stabilizing lib features
Browse files Browse the repository at this point in the history
The previous one was not following the process: it was a PR, which an
FCP was started on after the fact. This doesn't match what the stated
process is: we should instead link to an issue where t-libs started an
fcp, then a pr was written later.
  • Loading branch information
lf- committed Jun 12, 2021
1 parent 8608047 commit 882368f
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/stability.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@ To stabilize a feature, follow these steps:
- Add the appropriate labels: `@rustbot modify labels: +T-libs`.
- Link to the tracking issue and say "Closes #XXXXX".

You can see an example of stabilizing a feature at [#75132](https://github.com/rust-lang/rust/pull/75132).
You can see an example of stabilizing a feature at [#81656](https://github.com/rust-lang/rust/issues/81656).

## allow_internal_unstable

Expand Down

0 comments on commit 882368f

Please sign in to comment.