-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Epic: Make sure .NET libraries are continuously improved #44314
Comments
@terrajobst it feels like the documentation debt issue could be added as a user story in the description: Agree? Or should it be somewhere else / have its own epic? |
@carlossanlop yup, you can add a checkbox for it above then it will link up in https://dotnetepics.azurewebsites.net/ |
I think this issue should be moved to dotnet/runtime |
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. |
We'll be adding more proposed stories to the list above. |
I'll use this opportunity to bring these "grassroots" issues to attention:
Some of these would inspire joy and love in the community. |
What about APIs in |
#57209 was filed for items that will carry over to .NET 7. |
Summary
We'll use this epic to collect bottom-up improvements coming from the engineering team.
Dev features/work:
Developers can control TLS establishment in SocketsHttpHandler via a callback #46849These issues were not completed in .NET 6
The text was updated successfully, but these errors were encountered: