<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>.github/ISSUE_TEMPLATE/tracking_issue.md - fork/rust @ 1.44.0</title>
<meta name="description" content=".github/ISSUE_TEMPLATE/tracking_issue.md in fork/rust at 1.44.0.">
<meta property="og:title" content=".github/ISSUE_TEMPLATE/tracking_issue.md - fork/rust @ 1.44.0">
<meta property="og:description" content=".github/ISSUE_TEMPLATE/tracking_issue.md in fork/rust at 1.44.0.">
<meta property="og:type" content="website">
<meta property="og:site_name" content="git.julia.blue">
<link rel="stylesheet" href="/css/style.css?v=62">
<script type="module" src="/js/main.js?v=62"></script>
</head>
<body>
<main data-ref="1.44.0" data-tip="49cae55760da0a43428eba73abcb659bb70cf2e4">
<noscript>
  <div class="callout">
    <p>
      hey! this is a static git repo viewer. commit diffs, file history,
      older commits and other revisions won't load without javascript.
    </p>
    <p>
      you are still able to view source files on branch/tag tips,
      but the experience is degraded.
    </p>
  </div>
</noscript>
<header class="repo"><div>
<h1>fork/rust</h1>
</div>
<pre class="clone">git clone https://git.julia.blue/fork/rust</pre>
</header>
<p class="snapshot-commit"><span class="commit-author">bors</span><span class="commit-message" data-commit="49cae55760da0a43428eba73abcb659bb70cf2e4">Auto merge of #72883 - Mark-Simulacrum:stable-next, r=Mark-Simulacrum</span><span class="snapshot-sha sha" data-commit="49cae55760da0a43428eba73abcb659bb70cf2e4">49cae55760d</span><time datetime="2020-06-01T15:42:51+00:00" title="2020-06-01 15:42:51 +0000">2020-06-01</time></p>
<header class="topbar"><details class="switcher"><summary>1.44.0</summary><div class="menu"><strong>branches</strong><a href="/fork/rust/ref/master/">master</a><strong>tags</strong><a href="/fork/rust/ref/1.39.0/">1.39.0</a><a href="/fork/rust/ref/1.40.0/">1.40.0</a><a href="/fork/rust/ref/1.41.0/">1.41.0</a><a href="/fork/rust/ref/1.41.1/">1.41.1</a><a href="/fork/rust/ref/1.42.0/">1.42.0</a><a href="/fork/rust/ref/1.43.0/">1.43.0</a><a href="/fork/rust/ref/1.43.1/">1.43.1</a><a class="current" href="/fork/rust/ref/1.44.0/">1.44.0</a><a class="all" href="/fork/rust/refs">all refs →</a></div></details><nav class="crumbs"><a href="/fork/rust/">rust</a> / <a href="/fork/rust/ref/1.44.0/tree/.github/">.github</a> / <a href="/fork/rust/ref/1.44.0/tree/.github/ISSUE_TEMPLATE/">ISSUE_TEMPLATE</a> / <span class="cur">tracking_issue.md</span></nav>
<span class="view-stats"><span>2.3 KiB</span><span>58 lines</span></span><span class="actions"><a class="raw" href="/fork/rust/raw/51bf0c3ee673652e64d8770d189b2454f38277d3/.github/ISSUE_TEMPLATE/tracking_issue.md">raw</a></span></header>
<div class="markdown-view"><input type="radio" name="markdown-view" id="markdown-rendered" checked><label for="markdown-rendered">rendered</label><input type="radio" name="markdown-view" id="markdown-code"><label for="markdown-code">code</label><section class="readme rendered"><hr />
<h2>name: Tracking Issue
about: A tracking issue for an accepted feature or RFC in Rust.
title: Tracking Issue for XXX
labels: C-tracking-issue</h2>
&lt;!--
Thank you for creating a tracking issue! 📜 Tracking issues are for tracking a
feature from implementation to stabilisation. Make sure to include the relevant
RFC for the feature if it has one. Otherwise provide a short summary of the
feature and link any relevant PRs or issues, and remove any sections that are
not relevant to the feature.

Remember to add team labels to the tracking issue.
For a language team feature, this would e.g., be `T-lang`.
Such a feature should also be labeled with e.g., `F-my_feature`.
This label is used to associate issues (e.g., bugs and design questions) to the feature.
--&gt;
<p>This is a tracking issue for the RFC "XXX" (rust-lang/rfcs#NNN).
The feature gate for the issue is <code>#![feature(FFF)]</code>.</p>
<h3>About tracking issues</h3>
<p>Tracking issues are used to record the overall progress of implementation.
They are also uses as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however <em>not</em> meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.</p>
<h3>Steps</h3>
&lt;!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
--&gt;
<ul>
<li><input disabled="" type="checkbox"/>
Implement the RFC (cc @rust-lang/XXX -- can anyone write up mentoring
instructions?)</li>
<li><input disabled="" type="checkbox"/>
Adjust documentation (<a href="https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs">see instructions on rustc-dev-guide</a>)</li>
<li><input disabled="" type="checkbox"/>
Stabilization PR (<a href="https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr">see instructions on rustc-dev-guide</a>)</li>
</ul>
<h3>Unresolved Questions</h3>
&lt;!--
Include any open questions that need to be answered before the feature can be
stabilised.
--&gt;
<p>XXX --- list all the "unresolved questions" found in the RFC to ensure they are
not forgotten</p>
<h3>Implementation history</h3>
&lt;!--
Include a list of all the PRs that were involved in implementing the feature.
--&gt;
</section><div class="code-panel"><pre class="code src" data-hl=".github/ISSUE_TEMPLATE/tracking_issue.md"><span class="code-line"><a class="ln" id="L1" href="#L1">1</a><span class="code-text">---</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L2" href="#L2">2</a><span class="code-text">name: Tracking Issue</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L3" href="#L3">3</a><span class="code-text">about: A tracking issue for an accepted feature or RFC in Rust.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L4" href="#L4">4</a><span class="code-text">title: Tracking Issue for XXX</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L5" href="#L5">5</a><span class="code-text">labels: C-tracking-issue</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L6" href="#L6">6</a><span class="code-text">---</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L7" href="#L7">7</a><span class="code-text">&lt;!--</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L8" href="#L8">8</a><span class="code-text">Thank you for creating a tracking issue! 📜 Tracking issues are for tracking a</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L9" href="#L9">9</a><span class="code-text">feature from implementation to stabilisation. Make sure to include the relevant</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L10" href="#L10">10</a><span class="code-text">RFC for the feature if it has one. Otherwise provide a short summary of the</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L11" href="#L11">11</a><span class="code-text">feature and link any relevant PRs or issues, and remove any sections that are</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L12" href="#L12">12</a><span class="code-text">not relevant to the feature.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L13" href="#L13">13</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L14" href="#L14">14</a><span class="code-text">Remember to add team labels to the tracking issue.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L15" href="#L15">15</a><span class="code-text">For a language team feature, this would e.g., be `T-lang`.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L16" href="#L16">16</a><span class="code-text">Such a feature should also be labeled with e.g., `F-my_feature`.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L17" href="#L17">17</a><span class="code-text">This label is used to associate issues (e.g., bugs and design questions) to the feature.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L18" href="#L18">18</a><span class="code-text">--&gt;</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L19" href="#L19">19</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L20" href="#L20">20</a><span class="code-text">This is a tracking issue for the RFC &quot;XXX&quot; (rust-lang/rfcs#NNN).</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L21" href="#L21">21</a><span class="code-text">The feature gate for the issue is `#![feature(FFF)]`.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L22" href="#L22">22</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L23" href="#L23">23</a><span class="code-text">### About tracking issues</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L24" href="#L24">24</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L25" href="#L25">25</a><span class="code-text">Tracking issues are used to record the overall progress of implementation.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L26" href="#L26">26</a><span class="code-text">They are also uses as hubs connecting to other relevant issues, e.g., bugs or open design questions.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L27" href="#L27">27</a><span class="code-text">A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L28" href="#L28">28</a><span class="code-text">Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L29" href="#L29">29</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L30" href="#L30">30</a><span class="code-text">### Steps</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L31" href="#L31">31</a><span class="code-text">&lt;!--</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L32" href="#L32">32</a><span class="code-text">Include each step required to complete the feature. Typically this is a PR</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L33" href="#L33">33</a><span class="code-text">implementing a feature, followed by a PR that stabilises the feature. However</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L34" href="#L34">34</a><span class="code-text">for larger features an implementation could be broken up into multiple PRs.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L35" href="#L35">35</a><span class="code-text">--&gt;</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L36" href="#L36">36</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L37" href="#L37">37</a><span class="code-text">- [ ] Implement the RFC (cc @rust-lang/XXX -- can anyone write up mentoring</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L38" href="#L38">38</a><span class="code-text">      instructions?)</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L39" href="#L39">39</a><span class="code-text">- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L40" href="#L40">40</a><span class="code-text">- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L41" href="#L41">41</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L42" href="#L42">42</a><span class="code-text">[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L43" href="#L43">43</a><span class="code-text">[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L44" href="#L44">44</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L45" href="#L45">45</a><span class="code-text">### Unresolved Questions</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L46" href="#L46">46</a><span class="code-text">&lt;!--</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L47" href="#L47">47</a><span class="code-text">Include any open questions that need to be answered before the feature can be</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L48" href="#L48">48</a><span class="code-text">stabilised.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L49" href="#L49">49</a><span class="code-text">--&gt;</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L50" href="#L50">50</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L51" href="#L51">51</a><span class="code-text">XXX --- list all the &quot;unresolved questions&quot; found in the RFC to ensure they are</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L52" href="#L52">52</a><span class="code-text">not forgotten</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L53" href="#L53">53</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L54" href="#L54">54</a><span class="code-text">### Implementation history</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L55" href="#L55">55</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L56" href="#L56">56</a><span class="code-text">&lt;!--</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L57" href="#L57">57</a><span class="code-text">Include a list of all the PRs that were involved in implementing the feature.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L58" href="#L58">58</a><span class="code-text">--&gt;</span></span></pre></div></div>
</main>
</body>
</html>
