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/feature-lifecycle/api-change-proposals.md
+6-6
Original file line number
Diff line number
Diff line change
@@ -13,9 +13,9 @@ being solved and concrete motivating examples.
13
13
You can create an ACP in the `rust-lang/libs-team` repo using [this issue template](https://github.com/rust-lang/libs-team/issues/new?assignees=&labels=api-change-proposal%2C+T-libs-api&template=api-change-proposal.md&title=%28My+API+Change+Proposal%29).
14
14
15
15
Once a t-libs-api team member has reviewed the ACP and judged that it should
16
-
move forward they will second the ACP (via `@rfcbot second`) and initiate an
17
-
ICP (inital comment period). This initial comment period is intended to give
18
-
other stake holders a chance to participate in the initial discussion prior to
19
-
starting the implementation. Once this ICP has completed you should proceed
20
-
with the implementation of your proposal and then move on to the next step of
21
-
the feature lifecycle, creating a tracking issue.
16
+
move forward they will second the ACP and initiate an ICP (inital comment
17
+
period). This initial comment period is intended to give other stake holders a
18
+
chance to participate in the initial discussion prior to starting the
19
+
implementation. Once this ICP has completed you should proceed with the
20
+
implementation of your proposal and then move on to the next step of the
0 commit comments