Re: [Development] Requesting a repository for Qt Interface Framework Reference APIs

+1 for moving those to separate repo (as basically those are more sophisticated examples) The only question I've is Neptune3 UI still being kept alive (those were consumed there --​ Przemysław Nogaj Head of HMI Technology t:   +48 729 043 291 m: p...@spyro-soft.com

Re: [Development] Requesting a repository for Qt Interface Framework Reference APIs

Just to add another minor downside to the current name: qtif and qtifw are already quite common shorthands for Qt Installer Framework in search keywords / discussions. Elvis Den tors 7 dec. 2023 kl 20:03 skrev Maurice Kalinowski via Development : > > You are absolutely correct that this module st

Re: [Development] Requesting a repository for Qt Interface Framework Reference APIs

You are absolutely correct that this module started with a pure automotive focus, back then called Qt IVI. However, we recognized that its functionality can also be utilized in a generic way, which was the reason for the rename and generalization efforts done in the past. There might still be so

Re: [Development] Removal/deprecation of OpenSSL 1 in Qt

On Thu, 7 Dec 2023 at 12:33, Giuseppe D'Angelo wrote: > * For how long is QNX going to support OpenSSL 1? Is OpenSSL 3 support > on the radar? Yes, it's on the radar for QNX 8, which is not released yet. > Is there an online resource showing their commitment at > maintaining it? Is there the pos

Re: [Development] Requesting a repository for Qt Interface Framework Reference APIs

If it’s an option to rename this module we should take the opportunity to do so I think. The problem of the generic naming came up in the past, but the understanding was that it was too late to change. If that is not the case after all, we should strongly consider it. The documentation at http

Re: [Development] Requesting a repository for Qt Interface Framework Reference APIs

On Thursday, 7 December 2023 08:02:15 PST Tuukka Turunen via Development wrote: > So the question is what should this module be called, if it would be > renamed? I would indeed want to know what these are interfaces of or for. Like I said, they are not network interfaces, which is the first thin

Re: [Development] Nominating Semih Yavuz as an approver for the Qt project

+1 Disclosure: Semih is working in my team and we share the same office. Same for me best regards, Ulf -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

Re: [Development] Requesting a repository for Qt Interface Framework Reference APIs

Hi, Thiago is right, we can change the name as the module technically is not part of Qt release (https://download.qt.io/official_releases/qt/6.6/6.6.1/submodules/). That said, we can also decide not to change the name. Like mentioned by Dominik, it has existing since a while with the current n

Re: [Development] Removal/deprecation of OpenSSL 1 in Qt

Il 07/12/23 13:55, Kevin Kofler via Development ha scritto: Why is that Qt's problem? Qt does not and cannot check that all security updates for all dependencies have been applied, even when using a branch supported by upstream, so I do not see why this case would be any different. Because 1) Q

Re: [Development] Removal/deprecation of OpenSSL 1 in Qt

On Thursday, 7 December 2023 04:55:48 PST Kevin Kofler via Development wrote: > Qt should just use whatever OpenSSL is installed on the system and be done > with it. Chances are that any OpenSSL 1 it finds will be from some LTS > distro with backported security fixes anyway. I only agree partiall

[Development] Nominating Semih Yavuz as an approver for the Qt project

Hi, I would like to nominate Semih Yavuz for approver rights to the Qt project. Semih has been working on the Qt project since September 2022. He has been mainly focusing on the QML tooling story, including work on qmlformat and the QML language server. In addition, he is also taking care of t

Re: [Development] QT_WARNING_MSG/QT_DEPRECATED_HEADER

On Wednesday, 6 December 2023 23:58:10 PST Marc Mutz via Development wrote: > Hi, > > I've developed these to deprecate qspan_p.h in favour of qspan.h, but > we'll now just remove the old header instead. I can see us apply it to > qglobal.h, but not for 6.7. > > But if you have a use for a cross-

Re: [Development] Removal/deprecation of OpenSSL 1 in Qt

Giuseppe D'Angelo via Development wrote: > Innocent users may have their own build scripts that pull OpenSSL 1 and > build Qt against that, without realizing that they're playing with fire. > We should never expose users to insecure defaults, hence the opt-in > flag, and a build error if you ask fo

[Development] Meeting minutes from Qt Release Team meeting 05.12.2023

Qt 6.6 status: * Qt 6.6.1 released * Target is to release Qt 6.6.2 by the end of January 2024 Qt 6.7 status: * Platform and module freeze -milestone in effect * Qt 6.7 Feature Freeze will be in effect Fri 8th of December * Branching from 'dev' to '6.7' will happen Monday 11th

Re: [Development] Removal/deprecation of OpenSSL 1 in Qt

Hello, On 07/12/2023 09:50, Ville Voutilainen wrote: Well, this is straightforward in the sense that QNX doesn't support openssl3 yet. Dropping OpenSSL1 support is dropping support for TLS on QNX, and we don't want to do that. Sure, this is the premise of my mail, revert the change. What abou

Re: [Development] Removal/deprecation of OpenSSL 1 in Qt

On Thu, 30 Nov 2023 at 12:52, Giuseppe D'Angelo via Development wrote: > > Hi, > > OpenSSL 1 has reached EOL last September: > > > https://www.openssl.org/blog/blog/2023/09/11/eol-111/ > > > Qt has supported OpenSSL 3 for a while, and so last week I pushed a > patch to drop OpenSSL 1 support from