Should Quartz 4.0 only support modern .NET runtimes (6.0+)?

[lahma]

I'm beginning to question whether it makes sense to keep supporting full framework (,NET 4.8 and below) in v4 development. While it's still used a lot, the current 3.x is stable and feature rich and as such should cater for many needs. We can keep servicing 3.x with bug fixes and minimal improvements.

As resources are limited, it can be hard to justify trying to make things work both on Full Framework and the modern .NET 6.0. The plan would be to support at least the LTS release but probably keep support for longer time than needed.

[omrikaufman]

some products are hard to upgrade them to the .net core and should also enjoy the benefit of the new features in Quart .net 4

.net 4.8 support will be grate :)

[A9G-Data-Droid]

I normally suggest supporting framework as long as Microsoft does. Currently there is net472 and standard2.0 where targeting only standard2.0 would allow compatibility with Framework. So I would start by dropping net472 and announcing that framework will be cut at some point. A deprecation warning might get more attention than this poll.

[lahma]

The 3.x line is quite capable of supporting full framework usage. Mostly about downstream consumers understanding that 3.x is just fine and we don't need to upgrade unless (if even then) we are going to target modern runtimes.

We probably know for a fact that there's no big enterprise projects running on full framework relying on Quartz based on the sponsorships 😉