Skip to content

Commit 470b49b

Browse files
committed
Clarify how to quote and respond to the target tier policy requirements
Several times, people have seemed unclear on how to respond to some of the policy requirements, particularly those that just state things the target developers must *not* do (e.g. not posting to PRs that break the target). Add a note that such requirements just need acknowledgement, nothing more. Make quoting and responding a "must" rather than an "is encouraged to", since it's easier to review the requirements that way.
1 parent 42983a2 commit 470b49b

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

src/doc/rustc/src/target-tier-policy.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,8 +62,10 @@ not preclude an existing target's maintainers using issues (on the Rust
6262
repository or otherwise) to track requirements that have not yet been met, as
6363
appropriate; however, before officially proposing the introduction or promotion
6464
of a target, it should meet all of the necessary requirements. A target
65-
proposal is encouraged to quote the corresponding requirements verbatim as part
66-
of explaining how the target meets those requirements.
65+
proposal must quote the corresponding requirements verbatim and respond to them
66+
as part of explaining how the target meets those requirements. (For the
67+
requirements that simply state that the target or the target developers must
68+
not do something, it suffices to acknowledge the requirement.)
6769

6870
For a list of all supported targets and their corresponding tiers ("tier 3",
6971
"tier 2", "tier 2 with host tools", "tier 1", or "tier 1 with host tools"), see

0 commit comments

Comments
 (0)