diff options
| author | Guillaume Gomez <guillaume1.gomez@gmail.com> | 2021-05-03 15:08:12 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-05-03 15:08:12 +0200 |
| commit | 2d789b6373373e2ca783b5f8691c9ff80da383cf (patch) | |
| tree | 188fff60f7b92386d3ae2d3e117966817edb6638 /src | |
| parent | 55e21e8cca312556b3cf220b186675030b23fe02 (diff) | |
| parent | 9ed197b93c68bb08e39e1c04182d6adb3c20b076 (diff) | |
| download | rust-2d789b6373373e2ca783b5f8691c9ff80da383cf.tar.gz rust-2d789b6373373e2ca783b5f8691c9ff80da383cf.zip | |
Rollup merge of #84860 - badboy:link-to-mcp, r=GuillaumeGomez
Link to MCP from target tier policy Promoting new targets requires filing a MCP. Probably good to link to the documentation what that even is.
Diffstat (limited to 'src')
| -rw-r--r-- | src/doc/rustc/src/target-tier-policy.md | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/src/doc/rustc/src/target-tier-policy.md b/src/doc/rustc/src/target-tier-policy.md index a2cb0351916..cc02b294b44 100644 --- a/src/doc/rustc/src/target-tier-policy.md +++ b/src/doc/rustc/src/target-tier-policy.md @@ -102,7 +102,7 @@ place minimal requirements on the introduction of targets. A proposed new tier 3 target must be reviewed and approved by a member of the compiler team based on these requirements. The reviewer may choose to gauge -broader compiler team consensus via a Major Change Proposal (MCP). +broader compiler team consensus via a [Major Change Proposal (MCP)][MCP]. A proposed target or target-specific patch that substantially changes code shared with other targets (not just target-specific code) must be reviewed and @@ -223,8 +223,8 @@ patches that fail to build on a target. Thus, we place requirements that ensure the target will not block forward progress of the Rust project. A proposed new tier 2 target must be reviewed and approved by the compiler team -based on these requirements. Such review and approval may occur via a Major -Change Proposal (MCP). +based on these requirements. Such review and approval may occur via a [Major +Change Proposal (MCP)][MCP]. In addition, the infrastructure team must approve the integration of the target into Continuous Integration (CI), and the tier 2 CI-related requirements. This @@ -391,7 +391,7 @@ development platform, not just a compilation target. A proposed new tier 2 target with host tools must be reviewed and approved by the compiler team based on these requirements. Such review and approval may -occur via a Major Change Proposal (MCP). +occur via a [Major Change Proposal (MCP)][MCP]. In addition, the infrastructure team must approve the integration of the target's host tools into Continuous Integration (CI), and the CI-related @@ -648,3 +648,5 @@ for demotion of a tier 1 target (with or without host tools) requires a full RFC process, with approval by the compiler and release teams. Any such proposal will be communicated widely to the Rust community, both when initially proposed and before being dropped from a stable release. + +[MCP]: https://forge.rust-lang.org/compiler/mcp.html |