Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Top used controls from the major control vendors work well on ARM64 #70536

Closed
Tracked by #69887
jamshedd opened this issue Jun 10, 2022 · 2 comments
Closed
Tracked by #69887

Top used controls from the major control vendors work well on ARM64 #70536

jamshedd opened this issue Jun 10, 2022 · 2 comments
Assignees
Labels
arch-arm64 area-Meta Epic Groups multiple user stories. Can be grouped under a theme. Priority:1 Work that is critical for the release, but we could probably ship without
Milestone

Comments

@jamshedd
Copy link
Member

jamshedd commented Jun 10, 2022

Summary

Many if not most non-trivial client-side apps use popular third-party controls from control vendors. One key factor to unblocking porting of x64 apps to ARM64 will need to include the popular controls from these control vendors. We will need to partner with the control vendors to evangelize the need to add support for ARM64 where this doesn’t already exist.

Work for this scenario would include:

  • Inventory the top controls from these control vendors and their support for ARM64
  • Engage with the control vendors to help them add ARM64 support.

What does success look like (include a metric if possible)

  • Active engagements with the control vendors for ARM64
  • For top controls that do not support ARM64: a roadmap and commitment for adding this support

User Stories in this Epic:

  • Partnerships established with major control vendors
  • State of their controls known/understood
  • Action plan and roadmap built
@jamshedd jamshedd added Epic Groups multiple user stories. Can be grouped under a theme. Priority:1 Work that is critical for the release, but we could probably ship without labels Jun 10, 2022
@jamshedd jamshedd added this to the 7.0.0 milestone Jun 10, 2022
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@ghost
Copy link

ghost commented Jun 10, 2022

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

Summary

Many if not most non-trivial client-side apps use popular third-party controls from control vendors. One key factor to unblocking porting of x64 apps to ARM64 will need to include the popular controls from these control vendors. We will need to partner with the control vendors to evangelize the need to add support for ARM64 where this doesn’t already exist.

Work for this scenario would include:

  • Inventory the top controls from these control vendors and their support for ARM64
  • Engage with the control vendors to help them add ARM64 support.

What does success look like (include a metric if possible)

  • Active engagements with the control vendors for ARM64
  • For top controls that do not support ARM64: a roadmap and commitment for adding this support

User Stories in this Epic:

  • Partnerships established with major control vendors
  • State of their controls known/understood
  • Action plan and roadmap built
Author: jamshedd
Assignees: kalaskarsanket
Labels:

Epic, area-Meta, Priority:1

Milestone: 7.0.0

@jeffhandley jeffhandley modified the milestones: 7.0.0, Future Aug 11, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Feb 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-arm64 area-Meta Epic Groups multiple user stories. Can be grouped under a theme. Priority:1 Work that is critical for the release, but we could probably ship without
Projects
None yet
Development

No branches or pull requests

4 participants