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.

Sign up for GitHub

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

Jump to bottom

Drop UWP + use Uno.Sdk #1197

Open
kazo0 opened this issue Jul 16, 2024 · 2 comments
Open

Drop UWP + use Uno.Sdk #1197

kazo0 opened this issue Jul 16, 2024 · 2 comments
Labels
kind/api-change-breaking Categorizes issue or PR as related to breaking change to an existing API kind/enhancement New feature or request. kind/maintainer-experience Categorizes issue or PR as related to improving the experience of maintainers

Comments

@kazo0
Copy link
Contributor

kazo0 commented Jul 16, 2024

Following in the steps of Extensions (#2437), we should be dropping UWP support and the UWP samples as well as moving the projects and samples to use Uno.Sdk/single project
@kazo0 kazo0 added kind/api-change-breaking Categorizes issue or PR as related to breaking change to an existing API kind/enhancement New feature or request. labels Jul 16, 2024
@Xiaoy312
Copy link
Contributor

just to be clear, are we discontinuing the uwp line of packages?

@kazo0
Copy link
Contributor Author

kazo0 commented Jul 19, 2024

just to be clear, are we discontinuing the uwp line of packages?

Yes

@Xiaoy312 Xiaoy312 added the kind/maintainer-experience Categorizes issue or PR as related to improving the experience of maintainers label Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/api-change-breaking Categorizes issue or PR as related to breaking change to an existing API kind/enhancement New feature or request. kind/maintainer-experience Categorizes issue or PR as related to improving the experience of maintainers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Xiaoy312 @kazo0