@@ -24,12 +24,13 @@ occasionally ask what it would take to add a new tier 1 target. The Rust
24
24
project has no clear policy for target tiers. People not only don't know, they
25
25
don't know who to ask or where to start.
26
26
27
- See < https://forge .rust-lang.org/release /platform-support.html > for more
27
+ See < https://doc .rust-lang.org/nightly/rustc /platform-support.html > for more
28
28
information about targets and tiers.
29
29
30
- Once accepted, the policy sections of this RFC should be posted on
31
- < https://forge.rust-lang.org/ > in a "Target Tier Policy" section; this RFC will
32
- not be the canonical home of the up-to-date target tier policy.
30
+ Once accepted, the policy sections of this RFC should be posted alongside
31
+ < https://doc.rust-lang.org/nightly/rustc/platform-support.html > in a "Target
32
+ Tier Policy" section; this RFC will not be the canonical home of the up-to-date
33
+ target tier policy.
33
34
34
35
# Guide-level explanation
35
36
[ guide-level-explanation ] : #guide-level-explanation
@@ -101,7 +102,7 @@ requirements.
101
102
All supported targets and their corresponding tiers ("tier 3", "tier 2", "tier
102
103
2 with host tools", "tier 1", or "tier 1 with host tools") will be documented
103
104
on an appropriate official page, such as
104
- < https://forge .rust-lang.org/release /platform-support.html > .
105
+ < https://doc .rust-lang.org/nightly/rustc /platform-support.html > .
105
106
106
107
Note that a target must have already received approval for the next lower tier,
107
108
and spent a reasonable amount of time at that tier, before making a proposal
@@ -710,7 +711,7 @@ unlikely to provide value commensurate with that confusion.
710
711
711
712
This attempts to formalize and document Rust policy around targets and
712
713
architectures. Some requirements of such a policy appear on the [ Rust Platform
713
- Support page] ( https://forge .rust-lang.org/release /platform-support.html ) .
714
+ Support page] ( https://doc .rust-lang.org/nightly/rustc /platform-support.html ) .
714
715
715
716
Future expansions of such policy may find requirements from other communities
716
717
useful as examples, such as Debian's [ arch
0 commit comments