@@ -58,28 +58,8 @@ channels: stable, beta, and nightly.
5858 channel where unstable, incomplete, or experimental features are usable with
5959 feature gates.
6060
61- In order to implement a new feature, usually you will need to go through [ the
62- RFC process] [ rfc ] to propose a design, have discussions, etc. In some cases,
63- small features can be added with only an FCP ([ see below] [ break ] ). If in doubt, ask the
64- compiler, language, or libs team (whichever is most relevant).
65-
66- [ rfc ] : https://github.com/rust-lang/rfcs/blob/master/README.md
67-
68- After a feature is approved to be added, a tracking issue is created on the
69- ` rust-lang/rust ` repo, which tracks the progress towards the implementation of
70- the feature, any bugs reported, and eventually stabilization.
71-
72- The feature then needs to be implemented behind a feature gate, which prevents
73- it from being accidentally used.
74-
75- Finally, somebody may propose stabilizing the feature in an upcoming version of
76- Rust. This requires a Final Comment Period ([ see below] [ break ] ) to get the
77- approval of the relevant teams.
78-
79- After that, the feature gate can be removed and the feature turned on for all users.
80-
81- For more details on this process, see [ this chapter on implementing new
82- features.] ( ./implementing_new_features.md )
61+ See [ this chapter on implementing new features] ( ./implementing_new_features.md ) for more
62+ information.
8363
8464### Breaking Changes
8565
0 commit comments