nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-11-01 23:12:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

Rollup merge of #84860 - badboy:link-to-mcp, r=GuillaumeGomez

Browse Source 
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.
This commit is contained in:
Guillaume Gomez 2021-05-03 15:08:12 +02:00 committed by GitHub
commit 2d789b6373
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
src/doc/rustc/src/target-tier-policy.md
View File

@ -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