@@ -495,10 +495,9 @@ target. We hold tier 1 targets to our highest standard of requirements.
495495
496496A proposed new tier 1 target must be reviewed and approved by the compiler team
497497based on these requirements. In addition, the release team must approve the
498- long-term viability of the target, and the value of supporting the target. For
499- a tier 1 target, this will typically take place via a full RFC proposing the
500- target, to be jointly reviewed and approved by the compiler team and release
501- team.
498+ viability and value of supporting the target. For a tier 1 target, this will
499+ typically take place via a full RFC proposing the target, to be jointly
500+ reviewed and approved by the compiler team and release team.
502501
503502In addition, the infrastructure team must approve the integration of the target
504503into Continuous Integration (CI), and the tier 1 CI-related requirements. This
@@ -597,10 +596,10 @@ development platform, not just a compilation target.
597596
598597A proposed new tier 1 target with host tools must be reviewed and approved by
599598the compiler team based on these requirements. In addition, the release team
600- must approve the long-term viability of host tools for the target, and the
601- value of supporting host tools on the target. For a tier 1 target, this will
602- typically take place via a full RFC proposing the target, to be jointly
603- reviewed and approved by the compiler team and release team.
599+ must approve the viability and value of supporting host tools for the target.
600+ For a tier 1 target, this will typically take place via a full RFC proposing
601+ the target, to be jointly reviewed and approved by the compiler team and
602+ release team.
604603
605604In addition, the infrastructure team must approve the integration of the
606605target's host tools into Continuous Integration (CI), and the CI-related
0 commit comments