[Development] Let's drop MSVC 2019 for dev (6.8)

Jani Heikkinen jani.heikkinen at qt.io
Fri Feb 9 13:03:12 CET 2024


Hi!

I wouldn't once again duplicate these msvc binary packages if that isn't really mandatory; we already have so many packages and more is coming all the time so something has to be dropped as well. msvc2022 is quite old already so I would just replace msvc2019 with msvc2022 from Qt 6.8 ->

br,
Jani

From: Development <development-bounces at qt-project.org> On Behalf Of Vladimir Minenko via Development
Sent: perjantai 9. helmikuuta 2024 11.59
To: development at qt-project.org
Subject: Re: [Development] Let's drop MSVC 2019 for dev (6.8)

Hi,

I also think we should first get the 2022 compiler packages available for installation in parallel to the 2019 ones. This should be available for users for a while so that they have a transition period. Along with this, we should announce that the 2019 compiler will be dismissed by a specific date.

As we introduce Linux on ARM desktops and later Windows on ARM desktops, this can only be done IMHO after work on the release of 6.7 is finished, meaning in some of the 6.7.x slots.

Considering removal of MSVC 2019 in "Supported Configurations" in https://doc.qt.io/qt-6/windows.html should come after we provide a transition solution, IMHO

I fully appreciate the enthusiasm for using new capabilities in the newer compiler, but we should not forget the fact there are more users preferring the predictability of changes, and none like surprises with these topics.

--
Vladimir



On 6. Feb 2024, at 08:28, Allan Sandfeld Jensen <kde at carewolf.com<mailto:kde at carewolf.com>> wrote:

On Tuesday, 6 February 2024 06:57:34 CET Jani Heikkinen via Development wrote:

How about instead we drop at an LTS+2 release? The next one is actually
6.7.
We can't switch this in 6.7 at this point anymore; we don't have packages
for MSVC2022 at the moment and doing this (adding new packages + removing
ones) change this late of process is too risky
Could you please switch packaging to msvc2022 in dev then, so we don\t have
this discussion and excuse yet again in 6 months?

Br
Allan



--
Development mailing list
Development at qt-project.org<mailto:Development at qt-project.org>
https://lists.qt-project.org/listinfo/development

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20240209/e1372a2f/attachment-0001.htm>


More information about the Development mailing list