-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Internalize external dependencies #12048
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-enhancement
Milestone
Comments
smitpatel
added a commit
that referenced
this issue
Oct 22, 2018
Part of #12048 Comment: IAsyncQueryProvider
smitpatel
added a commit
that referenced
this issue
Oct 22, 2018
smitpatel
added a commit
that referenced
this issue
Oct 23, 2018
smitpatel
added a commit
that referenced
this issue
Oct 23, 2018
smitpatel
added a commit
that referenced
this issue
Nov 2, 2018
From today's discussions:
|
smitpatel
added
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
and removed
relinq-dependent
labels
Jun 3, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-enhancement
There is an ongoing discussion on how to improve our ability to service libraries like EF Core if things go really bad, e.g. if there is a security issue that needs to be patched urgently but we cannot wait for a dependency to be patched.
This issue is about executing on the plan resulting from the discussion, whatever it ends up being (the title assumes that it will require somehow internalizing some of our current dependencies, but it may end up looking different).
The text was updated successfully, but these errors were encountered: