[Development] Deciding on EOL for Visual Studio 2022

[Scott Bloom]

> >>When has this been announced?
> 
> A year ago, in CRA blog
> (http://qt.io/blog/preparing-for-the-european-cyber-resilience-act-cra
> )

You're saying that LTSes will be extracted from every four releases instead of every three. That's less work on us, so no big deal. Though people from KDAB ought to have known this...

Anyway, I think the proposal I made for VS2026 still makes sense for the Qt
Project:
* 2026-2027: toolchains 14.44 (VS2022), 14.50, sliding 14.51-53
* 2028-2029: toolchains 14.50, 14.54, sliding 14.55-57
* 2029-2030: toolchains 14.54, 14.58, sliding 14.59-61

This would mean Qt 6.12 still supports VS2022, but Qt 6.16 (Oct 2028) does not.

--
Just my 2 bits from a user POV.

Please allow 18 to 24 months before you REQUIRE 2026 for building a Qt project.  Meaning any new C++ features that 2026 has that 2022's latest patch does not support be held off in use in the public API for up to two years after the release of 2026.

I don’t know of any company that moves to the latest compiler before it has been stabilized and validated, which often takes up to two years.

Scott