Repository navigation
ImageSharp V3 should target .NET 6 Only #2072
Replies: 2 comments 2 replies
|
I do agree that this would make the code easier to maintain. There are a lot of |
|
Yeah, definitely no .NET Framework. LTS and future majors would also always target the latest LTS. All others would eventually follow suite once we get stable releases out. |
|
No objections as long as we setup a proper patching process for ImageSharp |
|
Yep agreed. There’s already release branches to branch from to create bug fix releases. |
Uh oh!
There was an error while loading. Please reload this page.
I've been putting a lot of thought to it and in order to avoid the increasing developmental distance between .NET Standard and .NET our V3 release should target .NET 6 will which be the current LTS release.
Using a .NET Standard target would mean that they cannot use any of the Runtime Intrinsics APIs. Adding an additional target to the old LTS .NET Core 3.1 would mean adding a target that reaches EOL in December 2022. I can't see us shipping V3 until after then.
Users currently targeting older frameworks will always have v2.1.0 to fall back on.
@SixLabors/core if any of you have any objection to this please let me know.
All reactions