|
8 | 8 |
|
9 | 9 | Promote the Arm aarch64-unknown-linux-gnu Rust target to Tier-1.
|
10 | 10 |
|
| 11 | +The next section provides a justification for the promotion. |
| 12 | + |
| 13 | +**Please note that the following are required next steps that should ideally emerge from ensuing discussions:** |
| 14 | + |
| 15 | + * An approval from the Compiler Team that Tier-1 target requirements have been met. |
| 16 | + |
| 17 | + * An approval from the Infrastructure Team that the target in question may be integrated into CI. |
| 18 | + |
| 19 | + * An approval from the Release Team that supporting the target in question is viable in the long term. |
| 20 | + |
| 21 | + |
11 | 22 | # Motivation
|
12 | 23 | [motivation]: #motivation
|
13 | 24 |
|
@@ -60,7 +71,7 @@ Please also note, by way of wilful disclosure, that this RFC's author is an empl
|
60 | 71 |
|
61 | 72 | The following section details how points 1 and 2 of the above assurances have either already been met or are close to being met.
|
62 | 73 |
|
63 |
| -Items in point 3 are addressed in the section titled [Unresolved Questions](#Unresolved-questions). That is not to say that they are unresolved per se but more that they are proposed next steps. |
| 74 | +As mentioned in the [summary](#Summary), items in 3 above are **required next steps.** |
64 | 75 |
|
65 | 76 | # Reference-level explanation
|
66 | 77 | [reference-level-explanation]: #reference-level-explanation
|
@@ -172,15 +183,7 @@ However, as emphasised in the narrative thus far, **the aarch64-unknown-linux-gn
|
172 | 183 | # Unresolved questions
|
173 | 184 | [unresolved-questions]: #unresolved-questions
|
174 | 185 |
|
175 |
| -The following points are 'unresolved' at present. From the author's PoV, these are next steps, subject to agreement with the RFC reviewers. |
176 |
| - |
177 |
| -**3.a. An approval from the Compiler Team that Tier-1 target requirements have been met.** |
178 |
| - |
179 |
| -**3.b. An approval from the Infrastructure Team that the target in question may be integrated into CI.** |
180 |
| - |
181 |
| -**3.c. An approval from the Release Team that supporting the target in question is viable in the long term.** |
182 |
| - |
183 |
| -The expectation is that these will get resolved as a result of the discussion that ensues with this RFC posting. |
| 186 | +No unresolved questions or issues remain. |
184 | 187 |
|
185 | 188 | # Future possibilities
|
186 | 189 | [future-possibilities]: #future-possibilities
|
|
0 commit comments