squiid/rust
1
0
Fork 0
Code Issues Pull requests Projects Activity

Auto merge of #86684 - inquisitivecrystal:libs-tracking-issue, r=m-ou-se

Browse source 
Fix typo in libs tracking issue template

Currently, the libs tracking issue template expands FCP as "final commenting period". Everywhere else, including in [the official explanation](https://rust-lang.github.io/rfcs/), it's expanded as "final comment period". That version also sounds a bit better. Accordingly, this PR changes the tracking issue template to use that version.

`@rustbot` label A-meta T-libs-api
r? `@m-ou-se`
This commit is contained in:
bors 2021-06-28 06:24:49 +00:00
parent d08a4718a9 fe54486352
commit 451e98e7b0
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
.github/ISSUE_TEMPLATE/library_tracking_issue.md vendored
View file

@ -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.
-->