Skip to content

remove reference to unsupported command #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 7, 2022
Merged

remove reference to unsupported command #41

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions src/feature-lifecycle/api-change-proposals.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,9 +13,9 @@ being solved and concrete motivating examples.
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).

Once a t-libs-api team member has reviewed the ACP and judged that it should
move forward they will second the ACP (via `@rfcbot second`) and initiate an
ICP (inital comment period). This initial comment period is intended to give
other stake holders a chance to participate in the initial discussion prior to
starting the implementation. Once this ICP has completed you should proceed
with the implementation of your proposal and then move on to the next step of
the feature lifecycle, creating a tracking issue.
move forward they will second the ACP and initiate an ICP (inital comment
period). This initial comment period is intended to give other stake holders a
chance to participate in the initial discussion prior to starting the
implementation. Once this ICP has completed you should proceed with the
implementation of your proposal and then move on to the next step of the
feature lifecycle, creating a tracking issue.