Demote `armv5te-unknown-linux-gnueabi` from Tier 2 (without host tools) to Tier 3

[jieyouxu]

Proposal

Demote armv5te-unknown-linux-gnueabi from Tier 2 without host tools to Tier 3.

This target does not have sufficient number of target maintainers, cf. Tier 2 Target Policy. Even before the last target maintainer removed themselves, this target still only had 1 target maintainer.

A tier 2 target must have a designated team of developers (the "target maintainers") available to consult on target-specific build-breaking issues, or if necessary to develop target-specific language or library implementation details. This team must have at least 2 developers.

According to Proposals, Approval and Stabilization, demoting a Tier 2 target will require:

If approved and affecting a tier 2 or tier 1 target, the change should be accompanied by a blog post announcing the change with a notice period of at least one release before the change applies.

I intend to draft a call-for-maintainer blog post where we will announce that this target is seeking target maintainers, and will be demoted to Tier 3 in the next release cycle if there are insufficient numbers of target maintainers (with a possibility of eventual removal if there are no interested target maintainers).

Warning

This MCP should not be seconded, demoting a Tier 2 target (according to the Forge docs) will require a FCP.

Mentors or Reviewers

Any

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 can formally be registered here by adding a comment.

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

Concerns can be lifted with:

@rustbot resolve reason-for-concern

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

cc @rust-lang/compiler

[jieyouxu]

Closing in favor of a more generic "Tier 2 targets that do not have any target maintainers" proposal.