dotnet / dotnet/maintenance-packages
Consider bringing back "unlikely to service" packages so that we have a place to build them
Open
- Dominant language
- C#
- Stars
- 44
- Forks
- 24
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 1
Description
Here's an interesting case for maintenance-packages: https://github.com/dotnet/runtime/issues/54341
Right now we don't build many of these packages any more because they no longer contain serviceable implementations - just facades / not-supported assemblies / reference assemblies. We could bring them back in maintenance-packages just to keep them building and update dependencies.
I think for this to be worthwhile we'd need to do it holistically and have enough customer value in doing so to warrant the work.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.