You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the context of a project goal reserving the bandwidth of a team,
the work of reviewing and revising proposed Reference text at this
time falls more on the T-lang-docs side rather than on the T-spec
side. So let's update the relevant project goals and the template
accordingly.
Copy file name to clipboardExpand all lines: src/TEMPLATE.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,18 +98,18 @@
98
98
99
99
> *If the feature has been RFC'd and implemented and experiences are positive, [stabilization](https://rustc-dev-guide.rust-lang.org/stabilization_guide.html) may be the right next step. In this case, you will need to author a first draft of text for the Rust reference and make a Team Ask to request someone from the the spec team to adapt that text for final inclusion. You will also need to author a stabilization report.
| Author stabilization report |*Goal point of contact, typically*||
107
+
| Author stabilization PR |*Goal point of contact, typically*||
108
+
| Stabilization decision |![Team][][lang]||
109
109
110
110
### Stabilize library feature
111
111
112
-
> *Standard library features follow the [libs-api stabilization process](https://rustc-dev-guide.rust-lang.org/stability.html#stabilizing-a-library-feature).
112
+
> *Standard library features follow the [libs-api stabilization process](https://rustc-dev-guide.rust-lang.org/stability.html#stabilizing-a-library-feature).
0 commit comments