mirror
/
rustc-dev-guide
mirror of https://github.com/rust-lang/rustc-dev-guide.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Define FCP where first used

This commit is contained in:
Mark Mansi 2019-11-26 17:24:19 -06:00 committed by Who? Me?!
parent efe3ab7ad1
commit 4edb95271d
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
src/walkthrough.md
View File

@ -120,13 +120,13 @@ itself to reflect the course of the discussion (e.g. new alternatives or prior
work may be added or you may decide to change parts of the proposal itself).
In the end, when the discussion seems to reach a consensus and die down a bit,
a rust team member may propose to move to FCP with one of three possible dispositions.
This means that they want the other members of the appropriate teams to review
and comment on the RFC. More discussion may ensue, which may result in more changes
or unresolved questions being added. At some point, when everyone is
satisfied, the RFC enters the "final comment period" (FCP), which is the last
chance for people to bring up objections. When the FCP is over, the disposition is
adopted. Here are the three possible dispositions:
a rust team member may propose to move to "final comment period" (FCP) with one
of three possible dispositions. This means that they want the other members of
the appropriate teams to review and comment on the RFC. More discussion may
ensue, which may result in more changes or unresolved questions being added. At
some point, when everyone is satisfied, the RFC enters the FCP, which is the
last chance for people to bring up objections. When the FCP is over, the
disposition is adopted. Here are the three possible dispositions:
- _Merge_: accept the feature. Here is the proposal to merge for our [`?` macro
feature][rfcmerge].