3.2 KiB
Microsoft.Data.SqlClient Roadmap
The Microsoft.Data.SqlClient roadmap communicates project priorities for evolving and extending the scope of the product. We encourage the community to work with us to improve SqlClient driver for these scenarios and extend it for others.
Released Versions
- Release Notes - For detailed release notes summarizing of all changes/features released.
- GitHub Releases - For downloading NuGet Packages and identifying driver releases with changelog notes.
Upcoming Ship Dates
| Milestone | Release Date | Project Board |
|---|---|---|
| Microsoft.Data.SqlClient v1.1 (servicing) | As needed (see also 1.1 releases) | Closed |
| Microsoft.Data.SqlClient v2.1 (servicing) | As needed (see also 2.1 releases) | Closed |
| Microsoft.Data.SqlClient v3.0 (servicing) | As needed (see also 3.0 releases) | Closed |
| Microsoft.Data.SqlClient v4.0 (servicing) | As needed (see also 4.0 releases) | Closed |
| Microsoft.Data.SqlClient v4.1 (servicing) | As needed (see also 4.1 releases) | Closed |
| Microsoft.Data.SqlClient v5.0 | GA (General Availability) estimated for May 2022 | SqlClient 5.0.0 |
Note: Dates are calendar year (as opposed to fiscal year).
SqlClient Projects are used by our development team to define roadmap of prioritized work. SqlClient Boards contain issues, pull requests, and other features, development activities that are categorized as cards. Our goal is to be transparent over priorities, work in progress and deliverables.
Milestone information is also available for GitHub Issues and Pull Requests dotnet/sqlclient milestones.
Feedback
The best way to give feedback is to create issues in the dotnet/sqlclient repo.
Although mostly obvious, please give us feedback that will give us insight on the following points:
- Existing features are missing some capability or otherwise don't work well enough.
- Missing features that should be added to the product.
- Design choices for a feature that is currently in-progress.
Some important caveats / notes:
- It is best to give design feedback quickly for improvements that are in-development. We're unlikely to hold a feature being part of a release on late feedback.
- We are most likely to include improvements that either have a positive impact on a broad scenario or have very significant positive impact on a niche scenario. This means that we are unlikely to prioritize modest improvements to niche scenarios.
- Compatibility will almost always be given a higher priority than improvements.