Policy: Require MCP and relevant team nominations for adding (ecosystem, custom codegen backend) testing jobs that would block PR/Merge CI and require documenting failure protocol

[jieyouxu]

Proposal

New policy: Require compiler MCP and a library team review for adding new ecosystem/integration test jobs/components to rust-lang/rust CI

The policy draft is at rust-lang/rust-forge#813. Please leave review feedback against that PR for the policy wording / details.

This policy is retroactive for existing ecosystem/integration test jobs/components

This requirement is intended to be retroactive. I will file MCPs for the existing ecosystem/integration test jobs/components (or at least partially; we will need to work with the ecosystem/integration test job/component maintainers to fill the details out). If they are accepted, then no actions need to be done. If there are outstanding blocking concerns, then we may modify or remove the existing ecosystem/integration test jobs/components if the concerns are substantial and cannot be resolved in a timely fashion (as a last resort).

Mentors or Reviewers

@davidtwco and @wesleywiser

This should also be discussed with T-{rustdoc,infra,bootstrap,libs} members.

Process

The main points of the Major Change Process are as follows:

• File an issue describing the proposal.
• A compiler team member or contributor who is knowledgeable in the area can second by writing @rustbot second.
  • Finding a "second" suffices for internal changes. If however, you are proposing a new public-facing feature, such as a -C flag, then full team check-off is required.
  • Compiler team members can initiate a check-off via @rfcbot fcp merge on either the MCP or the PR.
• Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.

You can read more about Major Change Proposals on forge.

[rustbot]

Important

This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

Concerns or objections to the proposal should be discussed on Zulip and formally registered here by adding a comment with the following syntax:

@rfcbot concern reason-for-concern 
<description of the concern> 

Concerns can be lifted with:

@rfcbot resolve reason-for-concern 

See documentation at https://forge.rust-lang.org

cc @rust-lang/compiler

[davidtwco]

@rustbot second

[apiraino]

@rustbot label -final-comment-period +major-change-accepted