Rollup merge of #86440 - rust-lang:libs-api-issue-template, r=m-ou-se
Update library tracking issue for libs-api rename.
This commit is contained in:
commit
90e5fe5f86
@ -2,7 +2,7 @@
|
||||
name: Library Tracking Issue
|
||||
about: A tracking issue for an unstable library feature.
|
||||
title: Tracking Issue for XXX
|
||||
labels: C-tracking-issue, T-libs
|
||||
labels: C-tracking-issue, T-libs-api
|
||||
---
|
||||
<!--
|
||||
Thank you for creating a tracking issue!
|
||||
@ -60,7 +60,7 @@ unresolved questions left, the feature might be ready for stabilization.
|
||||
If this feature didn't go through the RFC process, a final commenting period
|
||||
(FCP) is always needed before stabilization. This works as follows:
|
||||
|
||||
A library team member can kick off the stabilization process, at which point
|
||||
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
|
||||
|
Loading…
Reference in New Issue
Block a user