Updated instructions for tracking issue (#488)

* Updated instructions for tracking issue

Removed link to Forge instructions for documentation since they no longer seem to exist.

* Improved links and wording
This commit is contained in:
Alexander Regueiro 2019-11-01 17:36:47 +00:00 committed by Santiago Pastorino
parent 1e07320932
commit a14d795d7c
1 changed files with 6 additions and 6 deletions

View File

@ -99,15 +99,15 @@ for YOUR FEATURE".
For tracking issues for features (as opposed to future-compat
warnings), I don't think the description has to contain
anything specific. Generally we put the list of items required
for stabilization using a github list, e.g.
for stabilization in a checklist, e.g.,
```txt
**Steps:**
**Steps:**
- [ ] Implement the RFC (cc @rust-lang/compiler -- can anyone write
up mentoring instructions?)
- [ ] Adjust documentation ([see instructions on forge][doc-guide])
- Note: no stabilization step here.
- [ ] Implement the RFC. (CC @rust-lang/compiler -- can anyone write
up mentoring instructions?)
- [ ] Adjust the documentation. ([See instructions on rustc-guide.](https://rust-lang.github.io/rustc-guide/stabilization_guide.html#documentation-prs))
- [ ] Stabilize the feature. ([See instructions on rustc-guide.](https://rust-lang.github.io/rustc-guide/stabilization_guide.html#stabilization-pr))
```
<a name="stability-in-code"></a>