[Development] IPv6 support is required (but QNX gets a pass)

In trying to fix something in the CMake files, it turns out that we had accidentally disabled a part of our IPv6 support on some platforms. I'm trying to fix it with https://codereview.qt-project.org/c/qt/qtbase/+/499560 https://codereview.qt-project.org/c/qt/qtbase/+/499601 https://codereview.qt

[Development] CI failing due to ASan tst_selftest

See https://testresults.qt.io/coin/integration/qt/qtbase/tasks/1698516419 Two separate sets of changes are running into this problem, which means neither can be at fault. Tthis must be some other configuration that changed in the CI. The file in qt5.git that seems to control this build hasn't ch

Re: [Development] QtFluentMQ

Hello, Thanks for welcoming the project everybody. > AFAIR we haven't bike shedded over the commercial value of a new repository, > the architecture of the code it shall hold, or its licensing before. I don't > think we need to. To be fair, while we're Qtifying our API to give back to the commu

Re: [Development] QtFluentMQ

> On 26 Aug 2023, at 10:09, Ulf Hermann via Development > wrote: > > Hi, > > The usual way to request a repository, playground or not, is a mail like this: > > https://lists.qt-project.org/pipermail/development/2022-August/042900.html > > If the request is not totally outlandish it's usually

Re: [Development] On the use of the inline keyword

> On 25 Aug 2023, at 14:20, Ahmad Samir wrote: > > On 25/8/23 14:11, Cristian Adam via Development wrote: >> The other way of fixing this is by using ... macros. The article at c++ - >> Importing inline functions in MinGW - Stack >> Overflow

Re: [Development] QtFluentMQ

Hi, The usual way to request a repository, playground or not, is a mail like this: https://lists.qt-project.org/pipermail/development/2022-August/042900.html If the request is not totally outlandish it's usually granted, possibly after some bike shedding over the name and location. AFAIR w