From 809f4d1d3334b538cb1cd65e847a13faa77cee43 Mon Sep 17 00:00:00 2001 From: Yoh Deadfall Date: Thu, 5 Aug 2021 14:41:16 +0300 Subject: [PATCH] Fixed team responsible for stabilization (#1181) --- src/stability.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/stability.md b/src/stability.md index 7eff3e88b..51d849200 100644 --- a/src/stability.md +++ b/src/stability.md @@ -72,7 +72,7 @@ Furthermore this attribute is needed to mark an intrinsic as callable from To stabilize a feature, follow these steps: -0. Ask a **@T-libs** member to start an FCP on the tracking issue and wait for +0. Ask a **@T-libs-api** member to start an FCP on the tracking issue and wait for the FCP to complete (with `disposition-merge`). 1. Change `#[unstable(...)]` to `#[stable(since = "version")]`. `version` should be the *current nightly*, i.e. stable+2. You can see which version is @@ -82,7 +82,7 @@ To stabilize a feature, follow these steps: 3. If applicable, change `#[rustc_const_unstable(...)]` to `#[rustc_const_stable(since = "version")]`. 4. Open a PR against `rust-lang/rust`. - - Add the appropriate labels: `@rustbot modify labels: +T-libs`. + - Add the appropriate labels: `@rustbot modify labels: +T-libs-api`. - Link to the tracking issue and say "Closes #XXXXX". You can see an example of stabilizing a feature with