diff options
| author | bors <bors@rust-lang.org> | 2021-06-28 06:24:49 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2021-06-28 06:24:49 +0000 |
| commit | 451e98e7b02c8bf5e3bd5c9e780d51f7986a4408 (patch) | |
| tree | 0467d6931f4b704c21aaefe05b308ab804ae15b9 | |
| parent | d08a4718a9e3b9838a01345384d5b224b268daa1 (diff) | |
| parent | fe5448635293c299ad16d257e74e4af6b4e53ae3 (diff) | |
| download | rust-451e98e7b02c8bf5e3bd5c9e780d51f7986a4408.tar.gz rust-451e98e7b02c8bf5e3bd5c9e780d51f7986a4408.zip | |
Auto merge of #86684 - inquisitivecrystal:libs-tracking-issue, r=m-ou-se
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`
| -rw-r--r-- | .github/ISSUE_TEMPLATE/library_tracking_issue.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/.github/ISSUE_TEMPLATE/library_tracking_issue.md b/.github/ISSUE_TEMPLATE/library_tracking_issue.md index e879594b87a..32fccfcfb16 100644 --- a/.github/ISSUE_TEMPLATE/library_tracking_issue.md +++ b/.github/ISSUE_TEMPLATE/library_tracking_issue.md @@ -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. --> |