Skip to content

Latest commit

 

History

History
48 lines (31 loc) · 3.08 KB

roadmap.md

File metadata and controls

48 lines (31 loc) · 3.08 KB
Raw

.NET Core Roadmap

The .NET Core roadmap communicates project priorities for evolving and extending the scope of the product. New product experiences and features will include changes in various layers of the product, in some combination of the runtime, framework, language compilers and tools. Each component may have its own component-level roadmap that will available in the repo for that component.

The .NET Core team is currently focused on Web, Cloud, Microservices, Containers, and Console applications. We encourage the community to work with us to improve .NET Core for these scenarios and extend it for others.

Released Versions

For released versions of the product:

Upcoming Ship Dates

Milestone Release Date
.NET Core 2.1.x, 2.2.x, 3.0.x (servicing) Approximately every 1-2 months or as needed (see also releases)
.NET Core 3.1 LTS (Long Term Support) release, scheduled for December 2019
.NET 5.0 Release scheduled for November 2020
.NET 6.0 LTS (Long Term Support) release, scheduled for November 2021
.NET 7.0 Release scheduled for November 2022
.NET 8.0 LTS (Long Term Support) release, scheduled for November 2023

Details about longer-term schedule have been announced on 2019/5/6 in Introducing .NET 5 blog post.

Note: Dates are calendar year (as opposed to fiscal year).

Milestone information is available on most repos, for example dotnet/corefx milestones.

Feedback

The best way to give feedback is to create issues in the dotnet/core repo. You can also create issues in other .NET Core repos if you find that to be more appropriate for the topic you want to discuss.

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.