Slow moving orgs with brittle release processes are going to miss support deadlines anyway, it doesn’t matter if they arrive sooner or later.
Until the date hits them in the face there’s no urgency.
Until the date hits them in the face there’s no urgency.
It's not really Microsoft's job to work around your awkward requirements. Everything is open source, you can ship patches for .NET 6 yourself if you really want to.
Microsoft's general-ish LTS for .NET is 2 years. We also only seem to get a new release every 2 years. It's hard to handle breaking changes between two versions quickly.
What kind of breaking changes have been hard to handle?
Node (used at least as much as .NET and Java in enterprise) has a 3 year LTS cycle