Skip to content
This repository has been archived by the owner on Apr 22, 2024. It is now read-only.

Xamarin developers can target Windows with .NET 6 #12

Open
maddymontaquila opened this issue Oct 26, 2020 · 0 comments
Open

Xamarin developers can target Windows with .NET 6 #12

maddymontaquila opened this issue Oct 26, 2020 · 0 comments
Labels
Cost:XL Work that requires one engineer more than 4 weeks Priority:2 Work that is important, but not critical for the release Theme: great client app dev XP User Story A single user-facing feature. Can be grouped under an epic.

Comments

@maddymontaquila
Copy link
Member

maddymontaquila commented Oct 26, 2020

o Achieve parity around availability of various Forms controls and API’s (ie: Shell, CollectionView)
o Automate Windows UI tests

@maddymontaquila maddymontaquila added the User Story A single user-facing feature. Can be grouped under an epic. label Oct 26, 2020
@chrisntr chrisntr added the Priority:1 Work that is critical for the release, but we could probably ship without label Oct 28, 2020
@Redth Redth added the Cost:XL Work that requires one engineer more than 4 weeks label Oct 28, 2020
@maddymontaquila maddymontaquila changed the title Xamarin developers can target macOS and Windows with .NET 6 Xamarin developers can target Windows with .NET 6 Nov 13, 2020
@maddymontaquila maddymontaquila added Priority:2 Work that is important, but not critical for the release and removed Priority:1 Work that is critical for the release, but we could probably ship without labels Nov 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Cost:XL Work that requires one engineer more than 4 weeks Priority:2 Work that is important, but not critical for the release Theme: great client app dev XP User Story A single user-facing feature. Can be grouped under an epic.
Projects
None yet
Development

No branches or pull requests

3 participants