Re: [Development] Removal of Non-deprecated API Elements in v6.6.0
> On 19 Oct 2023, at 15:55, Phil Thompson via Development > wrote: > > On 19/10/2023 12:07, Giuseppe D'Angelo via Development wrote: >> On 19/10/2023 12:07, Phil Thompson via Development wrote: >>> Up until v6.6 upgrading to a new version was relatively low risk but this >>> will just
Re: [Development] Removal of Non-deprecated API Elements in v6.6.0
> On 19 Oct 2023, at 13:07, Giuseppe D'Angelo via Development > wrote: > > On 19/10/2023 12:07, Phil Thompson via Development wrote: >> Up until v6.6 upgrading to a new version was relatively low risk but this >> will just encourage people to stay on older versions. Is this a mistake or a >>
Re: [Development] Removal of Non-deprecated API Elements in v6.6.0
On 19/10/2023 12:07, Giuseppe D'Angelo via Development wrote: On 19/10/2023 12:07, Phil Thompson via Development wrote: Up until v6.6 upgrading to a new version was relatively low risk but this will just encourage people to stay on older versions. Is this a mistake or a change in policy?
Re: [Development] [Announce] Security advisory: Loading invalid QML image source impacts Qt
2023-10-19
Thread
List for announcements regarding Qt releases and development via Announce via Development
Correction to the post as I had the wrong URLs for the links to Codereview. The correct links are: dev: https://codereview.qt-project.org/c/qt/qtsvg/+/510674 6.6: https://codereview.qt-project.org/c/qt/qtsvg/+/510692 or
Re: [Development] Removal of Non-deprecated API Elements in v6.6.0
On 19/10/2023 12:07, Phil Thompson via Development wrote: Up until v6.6 upgrading to a new version was relatively low risk but this will just encourage people to stay on older versions. Is this a mistake or a change in policy? There is actually a policy document that says that certain source
[Development] Removal of Non-deprecated API Elements in v6.6.0
Hi, A number of API elements have been removed in v6.6.0. I haven't got an exhaustive list but QSqlResult::boundValues() will do as an example. The pre-6.6 implementation has been replaced by 2 new, incompatible, overloads. I completely agree with the reasons why this was desirable, my
[Development] [Announce] Security advisory: Loading invalid QML image source impacts Qt
2023-10-19
Thread
List for announcements regarding Qt releases and development via Announce via Development
Hi, An issue when loading an invalid QML image source has been reported and has been assigned the CVE id CVE-2023-45872. When an invalid source is used to indicate an image to be loaded is specified then it will end up trying to load it as a SVG file which will trigger a crash in Qt SVG.
