mirror of
https://github.com/rust-lang/rust
synced 2024-09-05 16:57:03 +00:00
Fix typo in libs tracking issue template
This commit is contained in:
parent
6830052c7b
commit
fe54486352
|
@ -50,20 +50,20 @@ If the feature is changed later, please add those PRs here as well.
|
|||
-->
|
||||
|
||||
- [ ] Implementation: #...
|
||||
- [ ] Final commenting period (FCP)
|
||||
- [ ] Final comment period (FCP)
|
||||
- [ ] Stabilization PR
|
||||
|
||||
<!--
|
||||
Once the feature has gone through a few release cycles and there are no
|
||||
unresolved questions left, the feature might be ready for stabilization.
|
||||
|
||||
If this feature didn't go through the RFC process, a final commenting period
|
||||
If this feature didn't go through the RFC process, a final comment period
|
||||
(FCP) is always needed before stabilization. This works as follows:
|
||||
|
||||
A library API team member can kick off the stabilization process, at which point
|
||||
the rfcbot will ask all the team members to verify they agree with
|
||||
stabilization. Once enough members agree and there are no concerns, the final
|
||||
commenting period begins: this issue will be marked as such and will be listed
|
||||
comment period begins: this issue will be marked as such and will be listed
|
||||
in the next This Week in Rust newsletter. If no blocking concerns are raised in
|
||||
that period of 10 days, a stabilzation PR can be opened by anyone.
|
||||
-->
|
||||
|
|
Loading…
Reference in a new issue