-
Notifications
You must be signed in to change notification settings - Fork 199
add rfc merge procedure #54
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.
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
Conversation
Add the following labels to the issue: | ||
|
||
- `B-rfc-approved` | ||
- `B-unstable` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think B-unstable
is only supposed to be applied when the impl has landed.
title: RFC Merge Procedure | ||
--- | ||
|
||
Once an RFC has been accepted (i.e., the final comment period is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably good to clarify that this is after an FCP where no serious new issues/arguments were raised.
🎊 |
Oh no, GitHub didn't show me @aturon 's comments. @nikomatsakis looks like you'll have to send in a second PR, sorry :/ |
There's no mention of what the title of the tracking issue should be. |
Also, Step 2. can be done much easier now with the new GitHub feature that lets you modify the PR branch by default - all I had to do was:
|
``` | ||
**Huzzah!** The @rust-lang/lang team has decided **to accept** this RFC. | ||
|
||
To track further discussion, subscribe to the tracking issue here: rust-lang/rust#41517 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This uses a specific number instead of a placeholder.
cc @steveklabnik