[Development] [Announce] Qt 6.2.11 Opensource released

2025-01-16 Thread List for announcements regarding Qt releases and development via Announce via Development
Hi all, we have released Qt 6.2.11 opensource today: * release note: https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.2.11/release-note.md * source packages in download.qt.io: * https://download.qt.io/archive/qt/6.2/6.2.11/ (note! All Qt6.2 downloads are now available

Re: [Development] Proposing to change https://wiki.qt.io/API_Design_Principles#Enums_in_classes to require scoped enums

2025-01-16 Thread Thiago Macieira
On Thursday 16 January 2025 07:13:50 Pacific Standard Time Mathias Hasselmann via Development wrote: > Do you really propose that we write > QRegularExpression::PatternOption::UseUnicodePropertiesOption in the > future? That's an identifier of 61 characters length. Considering my > thoughts about

Re: [Development] API style guide: scoped enum or not?

2025-01-16 Thread Marc Mutz via Development
On 16.01.25 15:05, Thiago Macieira wrote: > On Thursday 16 January 2025 04:55:56 Pacific Standard Time Marc Mutz via > Development wrote: >> https://gcc.godbolt.org/z/6exEonP5o, maybe? > > Yes. @Ville, @Peppe: do you happen to know whether this is supposed to work (using enum T when T is a typen

Re: [Development] Proposing to change https://wiki.qt.io/API_Design_Principles#Enums_in_classes to require scoped enums

2025-01-16 Thread Mathias Hasselmann via Development
Am 16.01.25 um 11:56 schrieb Marc Mutz via Development: Hi, Groundhog Day... Like every API review, so also in 6.9, we have the discussions between proponents of scoped vs. unscoped enums in class scope. Can we, please, settle this by strengthening the wording of https://wiki.qt.io/API_Design

Re: [Development] API style guide: scoped enum or not?

2025-01-16 Thread Thiago Macieira
On Thursday 16 January 2025 04:55:56 Pacific Standard Time Marc Mutz via Development wrote: > https://gcc.godbolt.org/z/6exEonP5o, maybe? Yes. -- Thiago Macieira - thiago.macieira (AT) intel.com Principal Engineer - Intel DCAI Platform & System Engineering smime.p7s Description: S/MIME cryp

Re: [Development] API style guide: scoped enum or not?

2025-01-16 Thread Marc Mutz via Development
On 05.05.23 08:10, Thiago Macieira wrote: > On Thursday, 4 May 2023 22:48:44 PDT Thiago Macieira wrote: >> On Thursday, 4 May 2023 22:28:44 PDT Thiago Macieira wrote: >>> But for those that use a very name, the API becomes cumbersome: >>>Qt::Alignment al = Qt::AlignmentFlag::Left; >>> >>> Can w

Re: [Development] Proposing to change https://wiki.qt.io/API_Design_Principles#Enums_in_classes to require scoped enums

2025-01-16 Thread Marc Mutz via Development
Hi Tor Arne, On 16.01.25 12:31, Tor Arne Vestbø wrote: > >> On Jan 16, 2025, at 11:56, Marc Mutz via Development >> wrote: >> >> Like every API review, so also in 6.9, we have the discussions between >> proponents of scoped vs. unscoped enums in class scope. > > Indicating that it’s still a nu

Re: [Development] Proposing to change https://wiki.qt.io/API_Design_Principles#Enums_in_classes to require scoped enums

2025-01-16 Thread Volker Hilsheimer via Development
> On 16 Jan 2025, at 11:58, Marc Mutz via Development > wrote: > > Hi, > > Groundhog Day... > > Like every API review, so also in 6.9, we have the discussions between > proponents of scoped vs. unscoped enums in class scope. Hi Marc, Taking this a step back: I recall that you agreed at t

Re: [Development] Proposing to change https://wiki.qt.io/API_Design_Principles#Enums_in_classes to require scoped enums

2025-01-16 Thread Marc Mutz via Development
Sorry for the double post; I blame Outlook's UI, and so should you ;) On 16.01.25 11:58, Marc Mutz via Development wrote: > Hi, > > Groundhog Day... > > Like every API review, so also in 6.9, we have the discussions between > proponents of scoped vs. unscoped enums in class scope. > > Can we, p

Re: [Development] Proposing to change https://wiki.qt.io/API_Design_Principles#Enums_in_classes to require scoped enums

2025-01-16 Thread Tor Arne Vestbø via Development
> On Jan 16, 2025, at 11:56, Marc Mutz via Development > wrote: > > Like every API review, so also in 6.9, we have the discussions between > proponents of scoped vs. unscoped enums in class scope. Indicating that it’s still a nuanced issue where each case might have different considerations

[Development] Qt 6.9.0 3rd party component update

2025-01-16 Thread Jani Heikkinen via Development
Hi everyone! It is time to check if some 3rd party component needs an update. Please check tasks assigned for you from https://bugreports.qt.io/browse/QTBUG-132849. Also, please inform me if task for some 3rd party stuff is missing. It would be really good to get all needed updates done latest

[Development] Proposing to change https://wiki.qt.io/API_Design_Principles#Enums_in_classes to require scoped enums

2025-01-16 Thread Marc Mutz via Development
Hi, Groundhog Day... Like every API review, so also in 6.9, we have the discussions between proponents of scoped vs. unscoped enums in class scope. Can we, please, settle this by strengthening the wording of https://wiki.qt.io/API_Design_Principles#Enums_in_classes to something that requires

Re: [Development] HEADS-UP: Qt 6.9 API change review

2025-01-16 Thread Jani Heikkinen via Development
Hi! The review is proceeding well, thanks for that! We are getting closer to the point where we need to agree on what has to be fixed before Qt 6.9.0 release and what's something we can live with. So please review open documents, if not already done. And MAINTAINERS: make sure open comments wi