|
| 1 | +--- |
| 2 | +name: Tracking Issue |
| 3 | +about: A tracking issue for a feature in Rust. |
| 4 | +title: Tracking Issue for XXX |
| 5 | +labels: C-tracking-issue |
| 6 | +--- |
| 7 | +<!-- |
| 8 | +Thank you for creating a tracking issue! 📜 Tracking issues are for tracking a |
| 9 | +feature from implementation to stabilisation. Make sure to include the relevant |
| 10 | +RFC for the feature if it has one. Otherwise provide a short summary of the |
| 11 | +feature and link any relevant PRs or issues, and remove any sections that are |
| 12 | +not relevant to the feature. |
| 13 | +
|
| 14 | +Remember to add team labels to the tracking issue. |
| 15 | +For a language team feature, this would e.g., be `T-lang`. |
| 16 | +Such a feature should also be labeled with e.g., `F-my_feature`. |
| 17 | +This label is used to associate issues (e.g., bugs and design questions) to the feature. |
| 18 | +--> |
| 19 | + |
| 20 | +This is a tracking issue for the RFC "XXX" (rust-lang/rfcs#NNN). |
| 21 | +The feature gate for the issue is `#![feature(FFF)]`. |
| 22 | + |
| 23 | +### About tracking issues |
| 24 | + |
| 25 | +Tracking issues are used to record the overall progress of implementation. |
| 26 | +They are also uses as hubs connecting to other relevant issues, e.g., bugs or open design questions. |
| 27 | +A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature. |
| 28 | +Instead, open a dedicated issue for the specific matter and add the relevant feature gate label. |
| 29 | + |
| 30 | +### Steps |
| 31 | +<!-- |
| 32 | +Include each step required to complete the feature. Typically this is a PR |
| 33 | +implementing a feature, followed by a PR that stabilises the feature. However |
| 34 | +for larger features an implementation could be broken up into multiple PRs. |
| 35 | +--> |
| 36 | + |
| 37 | +- [ ] Implement the RFC (cc @rust-lang/XXX -- can anyone write up mentoring |
| 38 | + instructions?) |
| 39 | +- [ ] Adjust documentation ([see instructions on rustc-guide][doc-guide]) |
| 40 | +- [ ] Stabilization PR ([see instructions on rustc-guide][stabilization-guide]) |
| 41 | + |
| 42 | +[stabilization-guide]: https://rust-lang.github.io/rustc-guide/stabilization_guide.html#stabilization-pr |
| 43 | +[doc-guide]: https://rust-lang.github.io/rustc-guide/stabilization_guide.html#documentation-prs |
| 44 | + |
| 45 | +### Unresolved Questions |
| 46 | +<!-- |
| 47 | +Include any open questions that need to be answered before the feature can be |
| 48 | +stabilised. |
| 49 | +--> |
| 50 | + |
| 51 | +XXX --- list all the "unresolved questions" found in the RFC to ensure they are |
| 52 | +not forgotten |
| 53 | + |
| 54 | +### Implementation history |
| 55 | + |
| 56 | +<!-- |
| 57 | +Include a list of all the PRs that were involved in implementing the feature. |
| 58 | +--> |
0 commit comments