Re: [Development] Challenge: adding new method overloads when existing consumers use {} with args

2022-07-28 Thread Thiago Macieira
[resent with my subscribed address, which means it won't arrive in kde-devel] [cross-posting to Qt dev ML - dunno if it'll arrive because I'm subscribed with different addresses] On Wednesday, 27 July 2022 14:54:55 PDT Friedrich W. H. Kossebau wrote: > And has no-one else yet run into this proble

Re: [Development] [Announce] Security advisory: Freetype in Qt

2022-07-28 Thread Albert Astals Cid
El dijous, 28 de juliol de 2022, a les 18:13:02 (CEST), Volker Hilsheimer va escriure: > The agreement is that KDE maintains patches like this for Qt 5 so that they > are available on top of the branches that are available to the Open Source > community. > https://dot.kde.org/2021/04/06/announci

Re: [Development] [Announce] Security advisory: Freetype in Qt

2022-07-28 Thread Volker Hilsheimer
Hey, > On 28 Jul 2022, at 17:31, Giuseppe D'Angelo via Development > wrote: > > Hi, > > On 27/07/2022 22:23, Thiago Macieira wrote: >> On Wednesday, 27 July 2022 11:47:20 PDT Giuseppe D'Angelo via Development >> wrote: >>> Right now, if one selects "LTS" and "Latest releases" (and *not* >>> "A

Re: [Development] [Announce] Security advisory: Freetype in Qt

2022-07-28 Thread Giuseppe D'Angelo via Development
Hi, On 27/07/2022 22:23, Thiago Macieira wrote: On Wednesday, 27 July 2022 11:47:20 PDT Giuseppe D'Angelo via Development wrote: Right now, if one selects "LTS" and "Latest releases" (and *not* "Archive"), one gets * 6.3.1 * 6.2.4 * 5.15.2 all of which are bugged AFAICT? Non-commercial cust

Re: [Development] [Announce] Security advisory: Freetype in Qt

2022-07-28 Thread Kevin Kofler via Development
Scott Bloom wrote: > Fully agreed with all your points, but knowing a release is LTS has value > even for those without support. > > I don't see a problem if someone is choosing a the latest LTS version, > getting that version since the current version is not a LTS. The Qt Company really needs to