Skip to content

Commit 0e08aaf

Browse files
committed
reframe well-tested comment around API design
1 parent 60625ff commit 0e08aaf

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/feature-lifecycle/stabilization.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ Stabilization goes through the Libs FCP[^1] process, which occurs on the [tracki
99

1010
## When is an FCP appropriate?
1111

12-
Once an unstable feature has been well-tested with no outstanding concerns, anyone may push for its stabilization.
12+
Once an unstable feature's API design space (e.g. alternative APIs) has been fully explored with no outstanding concerns, anyone may push for its stabilization.
1313

1414
If you're unsure if a feature is ready for stabilization the first step should be to ask in the relevant tracking issue and get assistance from other participants in that discussion. In some cases the tracking issue may not have many other active participants, so if you're ever having trouble getting any feedback please ping one of the [libs team reviewers](https://github.com/rust-lang/highfive/blob/master/highfive/configs/rust-lang/rust.json) directly to request assistance.
1515

0 commit comments

Comments
 (0)