Skip to content
Permalink
main
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
42 contributors

Users who have contributed to this file

@karelz @terrajobst @leecow @mairaw @Petermarcu @richlander @vivmishra @dcwhittaker @kalaskarsanket @NextNebula @OlivChu @teo-tsirpanis

.NET Release Schedule

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

If you're looking for the product roadmap, visit https://aka.ms/dotnet-product-roadmap.

Released Versions

For released versions of the product:

Upcoming Ship Dates

Milestone Release Date
.NET 6.0 LTS (Long Term Support) release. Approximately every 1-2 months or as needed.
.NET 7.0 STS (Standard Term Support) release. Approximately every 1-2 months or as needed.
.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.

Please give us feedback that will give us insight on the following points:

  • Existing features that 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.