When should we start dropping support for older .NET versions #18505
Replies: 2 comments
-
|
I vote to support the latest LTS and STS: .NET 10.0 & .NET 9.0 |
Beta Was this translation helpful? Give feedback.
-
|
I've just seen this now. My only concern is forcing people to update .NET (pulling requirements for their dev and hosting environments, potentially also dependencies with it) sooner. E.g., with the current approach, you needed to update .NET with 1.8 (which dropped .NET 6 and 7 support for 8) and will need with 3.0.0 (if we, following the patterns of before, only have .NET 10 support). In a faster approach they'd have needed to move to .NET 9 around 2.1.0. Obviously, you still need to move the same "distance" ultimately, just jumping from 8 to 10, but you aren't forced to update once a year, only every two years. But otherwise, with the new .NET support policy I don't really have a counter argument against keeping OC on the latest version at all times, i.e. Option D. Support would still be there for minor and patch versions. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Right we ship for 8 (LTS) and 9 (STS) because we want to support the latest version and also an LTS one (8). This was due to the fact that LTS (8) would be supported even after the current STS (9). Since recently this is not the case anymore: c.f. https://endoflife.date/dotnet
I would like to start a discussion about dropping older .NET versions support more quickly that we used to.
Are there reasons you wouldn't not be able to migrate from one version to the new one since STS and LTS now end at the same time and will get the same patches.
Beta Was this translation helpful? Give feedback.
All reactions