I’ve recently introduced tracking issues for all feature gates (except those used privately by rustc). You can see the list here – they are the issues marked T-lang and B-unstable.

These issues will soon be referenced from the feature gates themselves. For reference, here’s the current list:

There’s not a lot of detail on most of these issues, in part because many of these features are a bit obscure and it’s not clear exactly what needs to happen prior to stabilization or removal. Please leave comments on the issues if you know more about the trajectory for a particular feature.

This effort mirrors what we did earlier with unstable library APIs, and will feed into the dashboard we publish with each week’s subteam reports. We will also use these issues to track final comment periods for feature stabilization.