[Development] Meeting minutes from Qt Release Team meeting 07.11.2023

2023-11-07 Thread Jani Heikkinen via Development
Qt 6.6 status: * Qt 6.6.1 release preparations are ongoing * Branching from '6.6' to '6.6.1' will happen Tue 14th of November * Target is to release Qt 6.6.1 Thu 23rd of November Qt 6.7 status: * Platform and module freeze -milestone will be in effect 24th of November

Re: [Development] C++20 comparisons @ Qt (was: Re: C++20 @ Qt)

2023-11-07 Thread Thiago Macieira
On Tuesday, 7 November 2023 13:34:04 PST Marc Mutz via Development wrote: > > Yes. Remember that "one binary" is the process as loaded into memory, > > including all the libraries. Depending on compilation modes, inline > > functions may be merged from multiple independent libraries at runtime. >

Re: [Development] C++20 comparisons @ Qt (was: Re: C++20 @ Qt)

2023-11-07 Thread Marc Mutz via Development
On 07.11.23 20:12, Thiago Macieira wrote: > On Tuesday, 7 November 2023 06:28:51 PST Ivan Solovev via Development wrote: [...] >> The main reason to use `auto` is that it will allow us to avoid unnecessary >> `std::*_ordering -> Q*Ordering -> std::*_ordering` conversions in the C++20 >> case,

Re: [Development] C++20 comparisons @ Qt (was: Re: C++20 @ Qt)

2023-11-07 Thread Thiago Macieira
On Tuesday, 7 November 2023 09:07:10 PST Marc Mutz via Development wrote: > To be clear: This is not about Qt compiled with C++17 used in projects > compiled with C++20. This is about one .cpp file being compiled with > C++17 and another .cpp file from, broadly speaking, the same cmake > target,

Re: [Development] C++20 comparisons @ Qt (was: Re: C++20 @ Qt)

2023-11-07 Thread Thiago Macieira
On Tuesday, 7 November 2023 06:28:51 PST Ivan Solovev via Development wrote: > Hi, > > I'd like to discuss one more topic regarding the C++20 comparison. > > Can we allow an `auto` return type in helper functions and the three-way > comparison implementation for the built-in types? Answering

Re: [Development] Replacement for QFont::ForceIntegerMetrics in Qt 6?

2023-11-07 Thread Kai Uwe Broulik
Hi, thanks, QFont::PreferFullHinting seems to do the trick. I actually had that set for testing and thought QTextOption::setDesignMetrics(false) was the fix (after reading a bit of QFontEngineFT) but it was the hinting all along :-) Thanks! Cheers Kai Uwe Am 06.11.23 um 12:04 schrieb

Re: [Development] C++20 comparisons @ Qt (was: Re: C++20 @ Qt)

2023-11-07 Thread Marc Mutz via Development
On 07.11.23 15:28, Ivan Solovev via Development wrote: > > So, my question is - shoud we support mixing C++17 and C++20 in one binary? To be clear: This is not about Qt compiled with C++17 used in projects compiled with C++20. This is about one .cpp file being compiled with C++17 and another

Re: [Development] C++20 comparisons @ Qt (was: Re: C++20 @ Qt)

2023-11-07 Thread Ivan Solovev via Development
Hi, I'd like to discuss one more topic regarding the C++20 comparison. Can we allow an `auto` return type in helper functions and the three-way comparison implementation for the built-in types? The idea is that these methods can return `Q*Ordering` types in C++17 mode, and `std::*_ordering`

Re: [Development] Nominating QtGRPC & Qt Protobuf maintainers

2023-11-07 Thread Edward Welbourne via Development
Alex Blasche (6 November 2023 15:55) wrote: > Qt GRPC and Qt Protobuf were added to Qt a while ago. However until > now they have been in Tech Preview mode. As we investigate the > remaining issues which might prevent us from leaving TP, we need to > address the open issue of maintainer-ship. > >