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
Copy file name to clipboardExpand all lines: src/stabilization_guide.md
+10-12
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ following steps.
12
12
## Documentation PRs
13
13
14
14
If any documentation for this feature exists, it should be
15
-
in the `Unstable Book`, located at `src/doc/unstable-book`.
15
+
in the [`Unstable Book`], located at [`src/doc/unstable-book`].
16
16
If it exists, the page for the feature gate should be removed.
17
17
18
18
If there was documentation there, integrating it into the
@@ -63,8 +63,7 @@ The report should contain:
63
63
64
64
If any member of the team responsible for tracking this
65
65
feature agrees with stabilizing this feature, they will
66
-
start the FCP (final-comment-period) process by
67
-
commenting
66
+
start the FCP (final-comment-period) process by commenting
68
67
69
68
```bash
70
69
@rfcbot fcp merge
@@ -75,17 +74,14 @@ decision is to stabilize, we proceed to do the actual code modification.
75
74
76
75
## Stabilization PR
77
76
78
-
Once we have decided to stabilize a feature, we need to have a PR that
79
-
actually makes that stabilization happen. These kinds of PRs are a
80
-
great way to get involved in Rust, as they take you on a little tour
81
-
through the source code.
77
+
Once we have decided to stabilize a feature, we need to have
78
+
a PR that actually makes that stabilization happen. These kinds
79
+
of PRs are a great way to get involved in Rust, as they take
80
+
you on a little tour through the source code.
82
81
83
-
Here is a general guide to how to stabilize a feature -- every feature
84
-
is different, of course, so some features may require steps beyond
85
-
what this guide talks about.
82
+
Here is a general guide to how to stabilize a feature -- every feature is different, of course, so some features may require steps beyond what this guide talks about.
86
83
87
-
Note: Before we stabilize any feature, it's the rule that it should appear
88
-
in the documentation.
84
+
Note: Before we stabilize any feature, it's the rule that it should appear in the documentation.
0 commit comments