[Development] Plans of platforms in the CI and released binaries

[Tony Sarajärvi]

I did not know about ticket https://bugreports.qt.io/browse/QTBUG-74687 where discussions about Windows 7 in Qt6 have been discussed. Nor did apparently no one else in our meetings, since we were not told about those discussions.

Thus we got comments in https://codereview.qt-project.org/c/qt/qt5/+/285317 where we’re about to drop Windows 7 already in Qt5.15 ( according to these plans I’ve posted ), and to me it seems like the community doesn’t want to drop the support for Windows 7 in Qt 5.15 yet. But as usual, we could still have support for it, but drop it from the CI. But I can understand why that isn’t wanted.

So without anyone really responding to this thread, am I still to understand that you wish to have Windows 7 in Qt 5.15 CI? (and even if I get 2 replies that say “hell yeah”, those 2 might be the only 2 people in the world using that 😝)

-Tony

From: Development <development-bounces at qt-project.org> On Behalf Of Tony Sarajärvi
Sent: maanantai 30. joulukuuta 2019 11.20
To: development at qt-project.org
Subject: [Development] Plans of platforms in the CI and released binaries

Hi all!

We’ve had a few meetings here trying to figure out what we will have in the CI and ultimately what binaries we will serve in our releases.

Qt could support something that isn’t tested in the CI. We simply have to limit the amount of combinations we test due to technical limits of the CI infra. We try to cover to most common use cases however.

Also, for us to be able to produce binaries we release, it has to be in the CI, and also tested. So those facts are separated as own columns in this sheet I attached.

There’s the current 5.13 and 5.14 configurations visible and planned 5.15 and very much so planned Qt6.

Please go through it and respond with comments.

-Tony


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20200102/ca38cfa4/attachment.html>