dotnet-core/roadmap.md
Maira Wenzel 7b3160f1d0
Product roadmap (#5127)
* first draft

* add languages

* more content

* add some missing areas

* add spark

* add interactive

* Update F# 5 list for product roadmap (#5131)

* small changes

* Added CLI/SDK and Visual Basic sections

* Fixed bad formatting for CLI/SDK

* fix legend

* clean up text

* Add ML.NET

* add tye

* add winforms

* Update current.md

* Update current.md

* Update current.md

* Update current.md

* Update current.md

* Add gRPC

* More gRPC

* Remove required component parameters from Blazor roadmap

* table changes + wpf

* move table up

* Update current.md (#5144)

Xamarin roadmap work through end of 2020

* wpf updates

* Update current.md

* Update current.md

Co-authored-by: Phillip Carter <pcarter@fastmail.com>
Co-authored-by: Kathleen Dollard <kdollard@microsoft.com>
Co-authored-by: Jamshed Damkewala <jamshedd@users.noreply.github.com>
Co-authored-by: Sourabh Shirhatti <shirhatti@outlook.com>
Co-authored-by: Daniel Roth <daroth@microsoft.com>
Co-authored-by: David Ortinau <david.ortinau@microsoft.com>
2020-09-02 18:37:34 -07:00

2.5 KiB

.NET Release Schedule

This document covers the upcoming release dates for .NET and .NET Core.

If you're looking for the product roadmap, see the current roadmap document.

Released Versions

For released versions of the product:

Upcoming Ship Dates

Milestone Release Date
.NET Core 2.1.x (servicing) LTS (Long Term Support) release. Approximately every 1-2 months or as needed.
.NET Core 3.1.x (servicing) LTS (Long Term Support) release. Approximately every 1-2 months or as needed.
.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 May 6th, 2019 in Introducing .NET 5 blog post.

Milestone information is available on most repos, for example dotnet/runtime 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 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.