Following up on previous discussions we want to map out the plan for adding MultiArch to the main blocking CR views and ensure agreement.

Current 4.20-x86-vs-arm view can be used to gauge readiness. We should work through the process for investigating failures that show a higher rate in MultiArch and what that workflow is.

• Agree on configuration for 4.20-x86-vs-arm and have multi arch team monitor
• That configuration used for comparison will be what is eventually moved to the default view

That view currently is specifically targeting arm64 architecture jobs. We don't target specific jobs but variants like architecture, platform, etc. Our default view contains platforms aws, gcp, azure, metal, etc. Preference is to add the arm64 arch and support the default platform list.

• Agree on keeping only arm64 or adding heterogeneous
• Update the platform list to match default view and review if we need to classify individual jobs / platforms differently to filter from main view
   

tvardema Proposed being the point of contact for MultiArch regressions that are not also regressed / showing instability for amd64.  Discussed setting up a slack alias that can be assigned to additional people and using that vs. specifically relying on pinging Trevor.

Target goal date is end of September but preference is to enable before then. We will need agreement within the org to change the default views but we can work towards identifying what those changes are, monitoring and addressing any issues via the current comparison view and setting up any aliases / workflow for assigning regressions specific to MultiArch while seeking that agreement.